Cisco
Cisco 350-501: Model-Driven Telemetry for Networks Too Large to Poll
Polling works until the network becomes too large, the intervals become too coarse, or operators need to understand what happened between two snapshots. Model-driven telemetry changes the collection model by letting network devices stream structured operational data to collectors at a defined cadence or when state changes. That capability is now part of the Cisco 350-501 SPCOR exam and the Cisco CCNP Service Provider certification because provider assurance has to scale with the network it observes. Home/Cisco/Cisco 350-501: Model-Driven Telemetry for Networks Too Large to PollCiscoPublished October 3, 2026On this…
Cisco 350-501: Automating the Service Provider Core Safely
Service-provider automation is risky for the same reason it is valuable: one workflow can change thousands of devices consistently. At provider scale, manual CLI work becomes too slow and too variable, but a bad automated assumption can spread across the core in seconds. The Cisco 350-501 SPCOR exam and the Cisco CCNP Service Provider certification therefore treat automation, configuration management, Secure ZTP, model-driven interfaces, and telemetry as core operational skills. Home/Cisco/Cisco 350-501: Automating the Service Provider Core SafelyCiscoPublished October 3, 2026On this pageAutomation needs a source of truth before it…
Cisco 350-501: Carrier-Grade IPv6: Addressing Is the Easy Part
IPv6 addressing is usually the easiest part of a carrier IPv6 program. The hard work is preserving service behavior while customers, applications, access networks, peering, security controls, and legacy IPv4 continue to coexist. The current 350-501 SPCOR exam includes IPv6 routing and transition mechanisms because the CCNP Service Provider certification treats IPv6 as an operational architecture, not a longer version of an IP address. Home/Cisco/Cisco 350-501: Carrier-Grade IPv6: Addressing Is the Easy PartCiscoPublished October 3, 2026On this pageA provider IPv6 plan needs aggregation more than clever subnet conservationDual stack…
Cisco 350-501: Reading an MPLS VPN From Customer Edge to Provider Edge
An MPLS Layer 3 VPN is easiest to understand when the service is followed in one direction, from a customer edge router into the provider edge, across the core, and back out to another customer site. That end-to-end view matters for the 350-501 SPCOR exam because the CCNP Service Provider certification is not testing isolated acronyms; it expects engineers to understand how routing context, MP-BGP, route policy, and MPLS forwarding combine into a service. Home/Cisco/Cisco 350-501: Reading an MPLS VPN From Customer Edge to Provider EdgeCiscoPublished October 3, 2026On…
Cisco 350-501: Convergence, Scale, and Policy in Provider Routing
Service-provider routing design is an exercise in competing objectives. Faster convergence can consume more resources. More hierarchy can improve scale while hiding detail that some traffic-engineering decisions need. More policy control can protect business intent while increasing the number of ways an operator can accidentally suppress or redirect a route. The current 350-501 SPCOR exam and the CCNP Service Provider certification make sense only when those trade-offs are treated as architecture, not command memorization. Home/Cisco/Cisco 350-501: Convergence, Scale, and Policy in Provider RoutingCiscoPublished October 3, 2026On this pageConvergence is…
Cisco 350-701: DNS Security Belongs in the Threat Model
Home/Cisco/Cisco 350-701: DNS Security Belongs in the Threat ModelCiscoPublished October 3, 2026On this pageDNS creates a security decision before most application traffic beginsResolution reliability is part of the security designDomain blocking works best as a risk-reduction layerDNS tunneling changes the protocol from directory service to transportEncrypted DNS changes visibility, not the need for policyCache poisoning and redirection attack trust in the answerDNS logs become more valuable when identity and endpoint context are addedResponse should address the compromised system, not only the requested namePut DNS into architecture reviews and threat models…
Cisco 350-701: Zero Trust: Identity, Segmentation, Enforcement
Home/Cisco/Cisco 350-701: Zero Trust: Identity, Segmentation, EnforcementCiscoPublished October 3, 2026On this pageZero trust begins by replacing location with contextAuthentication is a gate, not the entire policySegmentation limits what a valid session can reachPolicy and enforcement should be designed as separate concernsDevice posture changes trust after the password is acceptedVisibility makes segmentation enforceable instead of theoreticalThreat response should be able to change network accessCloud and remote access extend the same trust modelA strong zero-trust design can explain every access decision Zero trust is easiest to misunderstand when it is reduced to…
Cisco 350-701: SASE Moves the Security Perimeter to the User
Home/Cisco/Cisco 350-701: SASE Moves the Security Perimeter to the UserCiscoPublished October 3, 2026On this pageThe old perimeter was convenient because applications were centralizedSSE is the security half of the modelIdentity becomes more important when network location is less stableNetworking still determines whether SASE feels usableDNS is an early enforcement point with broad coverageCASB and DLP focus on data behavior, not just destinationsSASE does not eliminate firewalls, VPNs, or campus controls overnightObservability has to follow the distributed pathThe architecture question is where trust is evaluated and enforced Secure Access Service Edge…
Cisco 350-701: Email Security Starts With Understanding the Attack Path
Home/Cisco/Cisco 350-701: Email Security Starts With Understanding the Attack PathCiscoPublished October 3, 2026On this pageThreat modeling begins with the attacker objectiveSender identity is useful evidence but not absolute proofLinks move the attack beyond the email systemAttachments require analysis without assuming every file is executableBusiness email compromise is an identity and process problemPost-delivery response matters because verdicts can changeOutbound email can expose data as well as deliver threatsUser reporting is a sensor, not an admission of failureFollow the attack path during both design and investigation Email security is not one filter…
Cisco 350-701: Endpoint Telemetry in the Right Workflow
Home/Cisco/Cisco 350-701: Endpoint Telemetry in the Right WorkflowCiscoPublished October 3, 2026On this pageCollect telemetry that supports a decisionProcess lineage often explains more than a single file hashPrioritization should reflect asset and identity contextRoute the signal to the team that can actAutomation should reduce repetitive delay without hiding judgmentEndpoint isolation is containment, not remediationTelemetry retention should support delayed discoveryEndpoint data becomes stronger when correlated with identity and network evidenceMeasure whether the workflow actually improves response Endpoint security products can produce enormous amounts of data: process launches, file activity, network connections, user…
Cisco 350-701: Network Detection and Response Sees What Firewalls Miss
Home/Cisco/Cisco 350-701: Network Detection and Response Sees What Firewalls MissCiscoPublished October 3, 2026On this pageFirewalls answer policy questions; NDR answers behavior questionsFlow telemetry provides wide coverage without full packet captureEast-west visibility exposes lateral movementEncrypted traffic still exposes useful metadataBaselines must adapt without learning attacks as normalNDR investigations need pivots, not just alertsIdentity context makes network behavior easier to interpretResponse should use NDR evidence to choose the least disruptive containmentFirewalls and NDR are complementary views of the same network Firewalls are essential enforcement points, but they do not observe every security…
Cisco 350-701: Secure Network Access With Cisco ISE Starts With Policy
Home/Cisco/Cisco 350-701: Secure Network Access With Cisco ISE Starts With PolicyCiscoPublished October 3, 2026On this pageDefine identities and access classes before touching the switchRADIUS carries the conversation between enforcement and policy802.1X is a framework for controlled access, not a magic checkboxProfiling helps classify devices but should not be mistaken for strong identityAuthorization should express business intent, not a maze of VLAN namesExceptions are part of the architecture, not an embarrassing edge casePosture and compliance should change authorization only when the signal is trustworthyThreat response can use ISE as an enforcement…
Cisco 350-701: Cloud Security Needs Context Across Identity and Network
Home/Cisco/Cisco 350-701: Cloud Security Needs Context Across Identity and NetworkCiscoPublished October 3, 2026On this pageIdentity is often the new control planeNetwork controls still matter because reachability shapes attack pathsPublic, private, and hybrid clouds change where controls are enforcedShared responsibility changes with the service modelCloud-delivered security controls need the same scrutiny as cloud workloadsTelemetry needs to connect identity, configuration, and network behaviorMisconfiguration is dangerous because cloud changes happen quicklyIncident response must cross cloud, identity, and network teamsReview cloud access as a complete path, not as separate control lists Cloud security becomes…
Cisco 350-701: VPN After Zero Trust: What Remote Access Still Needs
Home/Cisco/Cisco 350-701: VPN After Zero Trust: What Remote Access Still NeedsCiscoPublished October 3, 2026On this pageZero trust changes the unit of access from network to resourceVPN still fits when the task genuinely requires network reachabilityZTNA is strongest when applications can be published as discrete resourcesLegacy systems are usually the reason hybrid access survivesDevice posture matters more when credentials are no longer enoughAdministrative access deserves a stricter pattern than ordinary user accessRemote access must be observable after the connection succeedsAvailability and failure modes decide whether users bypass securityThe target architecture is…
Cisco 350-701: Security Automation Works Best on Repetitive Decisions
Home/Cisco/Cisco 350-701: Security Automation Works Best on Repetitive DecisionsCiscoPublished October 3, 2026On this pageStart with the manual decision before writing the playbookEnrichment is usually the lowest-risk place to beginDeterministic containment can be automated when the blast radius is smallAutomation needs identity, secrets, and least privilege of its ownIdempotency and rollback matter more than clever orchestrationHuman approval should sit at points of uncertainty, not everywhereAnalyst workflows should improve, not become harder to understandMetrics should measure decision quality, not only time savedTreat every playbook as production code Security automation is most useful…