Week 2 · Lesson 10

Security Solutions

Lesson 9 named the threats. This lesson names the tools that stop them. The organising idea is defense in depth: no single control is enough, so security is stacked in layers from the physical wall to the data itself. Each layer assumes the one outside it will eventually fail.

CCNA 200-301 Domain 5.0 Security Fundamentals Verified 2026-10-11
Part 1

Defense in depth

Defense in depth (layered security) means defending with many overlapping controls instead of one. If the firewall is bypassed, the intrusion-prevention system may catch the traffic; if that misses, endpoint protection may still stop the malware; if a host is compromised, encryption and segmentation limit what the attacker can reach. The goal is to make a successful attack so slow and noisy that it is either stopped or detected in time.

Definition — defense in depth. A security strategy that places multiple, independent layers of protection around the assets so that the failure of any one layer does not compromise the whole. Also called layered security.
Exam tip. If a question asks why a single firewall — or a single control of any kind — is not enough, the answer is always defense in depth: attackers who get past one layer meet others.
The five layers · select one to see its tools

Part 2

Firewalls and endpoint protection

A firewall enforces a security policy on traffic crossing between networks, usually at the edge between a trusted internal network and an untrusted one such as the Internet. It allows or denies traffic based on rules. Firewalls have evolved in capability.

Stateless or stateful? · pick the traffic and decide

TypeHow it decidesNotes
Packet-filtering firewallInspects each packet’s header in isolation — source/destination IP, protocol, and port.Simple and fast, but stateless: it cannot tell whether a packet is part of a legitimate session.
Stateful firewallKeeps a state table of active connections and allows return traffic for connections it already permitted.Smarter and the modern baseline; a reply to an allowed outbound request is automatically allowed back.

Endpoint protection

An endpoint is any device that could be the target or source of an attack — a PC, laptop, phone, server, or printer. Endpoint protection runs on the device itself.

Part 3

Access control lists

An access control list (ACL) is a written list of rules applied to a router or firewall interface. Each rule matches traffic (by source/destination address, protocol, or port) and the device takes the first matching rule — either permit or deny. ACLs are the simplest way to filter traffic at Layer 3 and Layer 4 and are a core CCNA configuration skill.

First match wins · step through the ACL
1 / 4
R1(config)# ip access-list extended FILTER
  10 permit tcp 192.168.10.0 0.0.0.255 any eq 80
  20 permit tcp any any eq 443
  30 deny   ip any any
  40 permit ip 10.0.0.0 0.255.255.255 any

Remember the order. ACLs are read top to bottom, first match wins. Because there is an implicit “deny all” at the end, a mistyped ACL can silently block everything. Order your permit rules before your deny rules.
Part 4

Secure remote access and VPNs

A virtual private network (VPN) creates an encrypted tunnel across an untrusted network such as the Internet, so that traffic is confidential and tamper-evident in transit.

TypeWho uses itWhat it connects
Site-to-site VPNTwo sites of the same organisationTwo gateways (for example two offices), transparently joining two networks.
Remote-access VPNAn individual userA single client (teleworker, laptop, phone) to the corporate network.

In a site-to-site VPN the branch router and the HQ router negotiate the tunnel themselves, so traffic between the two networks flows as if the sites were directly cabled and the users see no difference. In a remote-access VPN one individual connects in: a teleworker running a VPN client on a laptop creates a tunnel to the VPN gateway at the corporate edge, and their machine behaves as if it were plugged into the office network.

VPNs also replace insecure older remote protocols such as Telnet: instead of sending a clear-text login, administrators use SSH or a VPN to reach devices remotely.

Part 5

IDS vs IPS

Both intrusion systems watch traffic for signs of an attack; the difference is what they do about it — and that difference is entirely about where they sit in the path.

Where does it sit? · select the system
IDS — passive, taps the traffic Client Server IDS malicious traffic reaches the server IPS — inline, in the path Client Server IPS malicious traffic dropped here

SystemFull nameBehaviour
IDSIntrusion Detection SystemDetects and alerts. It is passive: it copies traffic, analyses it, and raises an alarm to an administrator.
IPSIntrusion Prevention SystemDetects and blocks. It sits inline in the traffic path and can drop or reset malicious packets in real time.
Exam tip. The single-letter difference is the whole question: D = detect (alerts), P = prevent (blocks). If an option says the device stops the attack, it is an IPS.
Part 6

Identity, physical security, encryption and monitoring

Authentication, authorisation, accounting

AAA is the framework that controls access to network devices and services:

Authentication is the first gate: until you have proved who you are, nothing else matters. Authorisation then decides what you may touch once inside — view-only access for some engineers, full configuration rights for others. Accounting turns a live network into evidence: who connected, when, to which device, and what they changed.

At a larger scale AAA is provided by a server such as Cisco ISE using the RADIUS or TACACS+ protocols. This lesson is only an introduction; Week 10 covers AAA configuration, patching, and device hardening in depth.

Physical security

Physical controls protect the equipment itself: locked server rooms, restricted-access cabinets, cable locks, surveillance cameras, and controlled entry. Physical security underpins everything else — an attacker with hands on a router can reset it or capture the console. In the lab you will connect to a router by console cable; in production that cable, and the room it lives in, must be physically protected.

Encryption

Encryption scrambles data so that only holders of the correct key can read it. It is the primary tool for confidentiality and, with integrity checks, for detecting tampering too. Two examples you will meet repeatedly:

Hashing is related but different: it produces a fixed-size fingerprint of data to verify integrity, and it is how device passwords are stored (as you will see with enable secret in the lab).

Security monitoring

Finally, you must watch the network. Log collection and a SIEM (Security Information and Event Management) system gather events from firewalls, routers, servers, and endpoints so that analysts can spot patterns an individual device would miss. Monitoring turns the logs from every other layer into a single picture of what is happening — and it is how a defence that failed to block becomes a defence that detects.

Part 7

Layer-to-tool map

This table maps each layer of defense in depth to its typical tools, so you can answer “which control belongs where” questions. The deeper configuration of AAA, patching, and device hardening is in Week 10.

Layer of defencePrimary toolsProtects mainly
PhysicalLocks, cabinets, access control, camerasAll goals — keeps hands off the gear
PerimeterFirewall (packet-filtering, stateful), VPNAvailability & confidentiality at the edge
NetworkACLs, IDS/IPS, segmentationConfidentiality & integrity of internal traffic
EndpointAntivirus/anti-malware, EDR, host firewallIntegrity & availability of hosts
Identity & dataAAA, encryption (TLS/IPsec), hashingConfidentiality & integrity of data and accounts
MonitoringLogs, SIEMDetection across every layer
Part 8 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 5.0 Security Fundamentals (5.5–5.8). cisco.com.
  2. NIST. SP 800-123: Guide to General Server Security (2008) — layered defence and host hardening. csrc.nist.gov.
  3. Rose, M. & Strom, D. RFC 2865: Remote Authentication Dial In User Service (RADIUS) (2000). rfc-editor.org/rfc/rfc2865.
  4. Kent, S. & Seo, K. RFC 4301: Security Architecture for the Internet Protocol (IPsec) (2005). rfc-editor.org/rfc/rfc4301.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.