Cisco 300-745 - Designing Cisco Security Infrastructure (300-745 SDSI) v1.0

The scenario described—where high CPU utilization prevents administrators from accessing device management interfaces—is a classic indication that the device'sControl Planeis being overwhelmed by malicious or malformed traffic (such as a DoS attack or a routing loop). To protect the "brains" of the network device,Control Plane Policing (CoPP)must be implemented.

CoPP allows an engineer to define filter and rate-limit policies specifically for traffic destined for the CPU. By categorizing traffic into different classes (e.g., routing protocols, management traffic like SSH, and "catch-all" untrusted traffic), CoPP ensures that critical management and control traffic is prioritized while excessive or suspicious traffic is dropped before it can impact the device’s performance. This maintainsoperational efficiencyeven during a traffic spike or attack. WhileAAA(Option B) handles authentication andRBAC(Option D) manages permissions once a user is logged in, neither can prevent the CPU exhaustion that blocks the login attempt in the first place.SNMP(Option C) is used for monitoring but does not provide active traffic policing. Within the Cisco SDSI framework, CoPP is a fundamental "Self-Defending Network" feature required to ensure the availability and resilience of the core infrastructure.

========

In modern cloud-native architectures, managing security for hundreds of microservices manually is unfeasible. To implementmutual TLS (mTLS)at scale within a Kubernetes cluster, aService Mesh(such as Istio or Cisco Service Mesh Manager) is the architectural solution of choice. A service mesh provides a dedicated infrastructure layer for handling service-to-service communication without requiring changes to the application code itself.

The service mesh operates by deploying a "sidecar" proxy alongside every service instance. These proxies handle the heavy lifting of identity verification, certificate rotation, and the establishment of encrypted tunnels. This ensures that every data exchange is encrypted and that services only communicate with authenticated peers. While anIngress Controller(Option A) manages traffic entering the cluster andLoad Balancing(Option B) distributes traffic, neither provides the granular, internal encryption framework required for pod-to-pod mTLS.Kubernetes Network Policies(Option C) act as a distributed firewall to allow or deny traffic based on IP/Port but do not handle encryption or cryptographic identity. By choosing a Service Mesh, the company satisfies the audit requirement for end-to-end encryption and pervasive visibility into the application's communication flow, aligning with Cisco's design principles for secure, scalable microservices.

========

To secure both wired and wireless access points against unauthorized devices, the industry-standard framework isIEEE 802.1x. This technology provides port-based network access control (PNAC), ensuring that no traffic—wired or wireless—is forwarded by the switch or access point until the device or user has been successfully authenticated by a central authority, typically a RADIUS server likeCisco Identity Services Engine (ISE).

In an 802.1x architecture, the device (Supplicant) must provide valid credentials or certificates to the switch/AP (Authenticator). The Authenticator then communicates with the Authentication Server to verify the identity. If authentication fails, the port remains in a "closed" state, effectively preventing the unauthorized "rogue" wired connections mentioned in the scenario. This approach is far more scalable and dynamic than manually shutting down ports or usingVACLs(Option C), which are static filters based on IP or MAC addresses.VxLANs(Option A) are used for network virtualization and overlay tunneling, whilePrivate VLANs(Option B) provide Layer 2 isolation within a subnet but do not verify identity. By implementing 802.1x, the construction company establishes a robust "gatekeeper" at the hardware level, satisfying the Cisco SDSI objective of securing the network edge through identity-based access control for a diverse set of devices.

========

A Security Operations Center (SOC) is often overwhelmed by thousands of alerts from various security tools. The primary tool used to aggregate, correlate, and—most importantly—prioritizethese incidents is theSecurity Information and Event Management (SIEM)system. According to the Cisco SDSI domain on Risk, Events, and Requirements, a SIEM acts as the central brain of the SOC.

A SIEM (such as Splunk or Cisco Secure Cloud Analytics) ingests logs from firewalls, endpoints, and cloud services. It uses correlation rules and risk-scoring algorithms to distinguish between low-priority "noise" and critical security incidents. For example, a single failed login might be ignored, but ten failed logins followed by a successful one and a large data transfer would be escalated as a high-priority incident.Endpoint Detection and Response (EDR)(Option B) andEndpoint Protection Platforms (EPP)(Option D) provide deep visibility and protection on individual hosts but lack the cross-platform correlation needed to prioritize organizational risk.CloudWatch(Option C) is a monitoring service for AWS resources but does not function as a multi-source security correlation engine. By using a SIEM, SOC analysts can focus their limited time on the most impactful threats, ensuring a more efficient and effective incident response process.

========

A SYN flood attack is a classic Denial-of-Service (DoS) technique that exploits the TCP three-way handshake. By sending a massive volume of SYN packets without completing the handshake, the attacker exhausts the target server's connection table.Cisco Secure Firewall(formerly Firepower) is the architectural component designed to mitigate these network-layer threats.

Cisco Secure Firewall utilizes features such asTCP InterceptandSYN Cookiesto defend against these attacks. When a SYN flood is detected, the firewall can act as a proxy for the handshake, only passing the completed connection to the backend server once the three-way handshake is verified. This prevents the server's resources from being overwhelmed by "half-open" connections.

In contrast,Cisco Web Security Appliance(Option A) is focused on web-based (HTTP/HTTPS) threats and proxying, not low-level TCP flood mitigation.Cisco Umbrella(Option B) primarily provides DNS-layer security and Secure Internet Gateway (SIG) services, which are ineffective against a direct SYN flood targeting an on-premises or cloud-hosted gaming server.Cisco Secure Endpoint(Option C) protects individual hosts from malware but cannot protect the network infrastructure or the server's TCP stack from being saturated by high-volume flood traffic. Consequently, Cisco Secure Firewall is the essential product for managing and mitigating these infrastructure-level network attacks.

========

In modern DevSecOps, managing third-party dependencies is a major security challenge.Dependabot(often stylized as Depend-a-bot) is the specific GitHub feature designed to automate the identification and updating of vulnerable dependencies. It works by scanning the application's manifest files (like package.json or requirements.txt) and analyzing thesemantic versioningof the included libraries.

When a known vulnerability (CVE) is reported in a specific version of a library used by the application, Dependabot flags the security risk and alerts the development team. Most importantly, it can automatically generate pull requests to upgrade the dependency to the minimum secure version that resolves the vulnerability. This ensures that the application remains secure without requiring manual tracking of every third-party component.

WhileGitHub Actions(Option C) can be used to run security scanners (like SAST tools), it is a general automation framework, not a dedicated dependency analysis tool.Artifact attestations(Option D) are used to prove the provenance and integrity of a build, andSealed boxes(Option B) is not a standard GitHub security feature related to vulnerability scanning. Utilizing Dependabot directly supports the Cisco SDSI objective of "Securing the CI/CD pipeline" by proactively managing the Software Bill of Materials (SBOM) and ensuring that vulnerable components do not reach the production environment.

In the aftermath of a security breach, forensic investigators rely on theAccountingportion ofAAA (Authentication, Authorization, and Accounting)to reconstruct a timeline of events. While Authentication verifies identity and Authorization defines permissions, Accounting is the specific framework used to track user activity, including login/logout times and the specific commands executed during a session.

According to Cisco Security Infrastructure design objectives, implementing a centralized AAA solution (such asCisco Identity Services Engine (ISE)or a TACACS+/RADIUS server) is critical for accountability. In this scenario, the engineer would query the AAA logs to identify exactly "who" accessed the sales system during the compromise period.SNMP(Option A) is primarily for network monitoring and performance data, not granular user access logs.NACM(Option B) is an access control model for NETCONF but doesn't provide the broad auditing required here.PKI(Option D) provides the certificates used for digital signatures and encryption but does not log the historical "session" data needed for the investigation. Therefore, AAA is the fundamental architectural requirement for ensuring non-repudiation and providing the audit trail necessary to satisfy risk management and incident response requirements.

========

Accidental exposure of sensitive credentials, such as API keys or AWS secrets, is a major risk in modern DevOps environments. To prevent such incidents from occurring, the most effective technical control is the implementation of aSource Code Management (SCM) precommit hook. A precommit hook is a script that runs locally on a developer's machine before a commit is finalized and pushed to a remote repository.

According to Cisco's DevSecOps design principles, precommit hooks can be configured to scan the code for specific patterns that resemble secrets (e.g., regex for AWS Access Key IDs). If the scanner detects a secret, it automatically aborts the commit, forcing the developer to remove or properly encrypt the sensitive data before the code can leave their local machine. This provides an immediate "shift-left" safety net that stops the leak at the source.

While aWeb Application Firewall (WAF)(Option A) protects against external attacks andPort Security(Option B) manages Layer 2 access, neither can prevent a developer from pushing code to GitHub. Aphishing education campaign(Option C) is beneficial for general security awareness but does not provide the automated, technical enforcement required to block credential leakage. By configuring precommit hooks, the pharmaceutical company establishes a proactive defense mechanism that significantly reduces the risk of credential exposure and aligns with the automation objectives of the Cisco SDSI curriculum.

In the realm of modern application security and Kubernetes networking,Ciliumhas emerged as the industry-standardContainer Network Interface (CNI)that leverageseBPF (extended Berkeley Packet Filter)technology. For a global company modernizing a monolithic app into microservices, Cilium provides the required scalability and high-performance networking by operating directly within the Linux kernel.

Unlike traditionalSecurity Groups(Option A) which are often limited to IP-based rules at the cloud infrastructure level, orENIs(Option C) which are AWS-specific hardware interfaces, Cilium providesidentity-awaresecurity. It understands Kubernetes labels and metadata, allowing for granular Layer 7 policy enforcement. Furthermore, Cilium addresses the "visibility and observability" requirement through itsHubblecomponent, which provides deep insights into network flows, application dependencies, and security events without the overhead of traditional sidecar proxies. AnIngress Gateway(Option D) manages external traffic entering the cluster but does not provide the comprehensive pod-to-pod networking, eBPF-based security, or internal observability that a CNI like Cilium offers. Designing with Cilium aligns with Cisco's focus on cloud-native security and the use of eBPF for distributed firewalling and telemetry in modern application environments.

========