Category Archives: Cisco
Storage networking carries traffic whose performance and failure behavior can directly determine whether applications remain available. The current 350-601 DCCOR v1.1 blueprint includes storage networking as a core domain, and the useful design review starts with the data path: host initiator, fabric, target, logical storage, multipathing, and the application that depends on the I/O. The […]
Data-center routing design has to move traffic quickly and predictably while limiting failure scope. The current 350-601 DCCOR v1.1 blueprint includes OSPFv2/OSPFv3, MP-BGP, PIM, first-hop redundancy, packet flow, VXLAN EVPN, and external connectivity. The important design decision is which protocol owns each layer and how much state each device must carry when the fabric grows […]
Nexus switching diagrams usually show leafs, spines, vPC pairs, uplinks, and servers. They rarely show software lifecycle, feature dependencies, control-plane limits, configuration checkpoints, logging, telemetry, automation, and the operational work required when a switch is partially healthy. The current 350-601 DCCOR v1.1 blueprint includes switching protocols, software updates, configuration management, monitoring, streaming telemetry, and Nexus […]
VXLAN EVPN is designed to make large Layer 2 and Layer 3 fabrics more scalable and controllable, but the security and operational value depends on how the underlay, overlay, endpoint learning, route distribution, anycast gateways, and external connectivity are designed. The current 350-601 DCCOR v1.1 blueprint explicitly includes VXLAN EVPN, MP-BGP, packet flow, and routing/switching […]
Cisco ACI policy becomes confusing when operators treat every object as a configuration requirement instead of as part of one forwarding decision. The current 350-601 DCCOR v1.1 blueprint still includes ACI fabric setup, access policies, VMM integration, network configuration management, and packet-flow analysis. The practical question is how tenants, VRFs, bridge domains, endpoint groups, contracts, […]
Enterprise security architecture rarely fails because a campus firewall, data-center segmentation policy, or cloud control is individually weak. It fails when the organization assumes the same trust model and enforcement pattern can be copied across environments that behave differently. The current 350-701 SCOR v2.0 scope makes this a timely design problem because modern security now […]
Zero trust is most useful when it is treated as a set of testable access assumptions rather than as a product category. The current 350-701 SCOR v2.0 blueprint includes zero-trust architecture, Cisco Duo Trust Monitor, MFA, Device Trust, health checks, Adaptive Access, SSO, secure private access, secure internet access, posture, and network access controls. The […]
Security automation becomes dangerous when a script can change policy faster than the organization can understand the change. The current 350-701 SCOR v2.0 blueprint includes interpreting Python scripts that call security-appliance APIs, secure network management through APIs/RESTCONF/NETCONF, DevSecOps, and orchestration/automation of security events. The core design problem is not whether an API call works; it […]
Threat detection is not the same as incident response. A detection is a claim that observed evidence matches a suspicious pattern. An incident workflow decides whether that claim represents harmful activity, what scope exists, what must be contained, which evidence must be preserved, and how the organization returns to a trusted state. The current 350-701 […]
Security telemetry is valuable only when the team knows what each signal can and cannot prove. The current 350-701 SCOR v2.0 blueprint includes security monitoring and telemetry, secure syslog, cloud logging ingestion into Splunk, network visibility with telemetry and native AI/ML, and XDR/SIEM/SOAR. More logs are not automatically more visibility; visibility exists when evidence can […]
Segmentation is often presented as a diagram full of colored boxes, but the real security value comes from the traffic the design prevents and the enforcement points that can prove it. The current 350-701 SCOR v2.0 blueprint explicitly includes segmentation using VLANs or Security Group Tags, Layer 2 defenses, firewall/IPS deployment models, cloud workload security, […]
Network access control is easy to reduce to 802.1X configuration. The current 350-701 SCOR v2.0 scope is broader: guest services, profiling, posture, BYOD, device compliance, application control, 802.1X, MAB, Cisco ISE, CoA, and zero-trust identity context. The architecture works only when identity evidence, policy, edge enforcement, and operational ownership stay aligned. The foundation in network […]
Hybrid cloud security fails when teams treat ‘on-premises’ and ‘cloud’ as two boxes joined by a trusted network link. The current 350-701 SCOR v2.0 blueprint explicitly covers hybrid environments, cloud shared-responsibility models, CASB, Multicloud Defense, Secure Workload, cloud logging, workload security, eBPF, and DevSecOps. The architecture problem is preserving identity, policy, segmentation, secrets, and evidence […]
Endpoint protection becomes more useful when prevention, detection, posture, inventory, and device management are treated as separate controls that exchange evidence. The current 350-701 SCOR v2.0 scope explicitly includes EPP, EDR, MDM/asset inventory, posture assessment, Cisco Secure Client, Cisco Secure Malware Analytics, Secure Endpoint antimalware, and interpretation of malware-detection events. The starting point is security […]
Web and email inspection controls sit in the path between users and some of the most abused application channels in enterprise security. The current 350-701 SCOR v2.0 scope includes URL filtering, malware protection, Secure Internet Access, data-loss prevention, email threat defense, phishing controls, and inspection of encrypted traffic. The useful question is not whether inspection […]
