Security Program and Wireless Security
Technology is only one layer of defence. A real security program adds people and policy: awareness training, physical access controls, and procedures that make the controls stick. Then this lesson turns to the network everyone connects through every day — Wi-Fi — and sorts the alphabet soup of WPA2, WPA3, AES-CCMP, SAE, and 802.1X/EAP into a decision tree you can defend on the exam.
- Name the elements of a security program: user awareness, training, and physical access control.
- Explain why people are the weakest link and how training compensates.
- Order the WLAN security protocols from open to WPA3.
- Distinguish personal (PSK) from enterprise (802.1X/EAP) authentication.
- Explain AES-CCMP, why TKIP is deprecated, and what SAE improves in WPA3.
- Match the right WLAN standard to the right deployment scenario.
What a security program is
A security program is the whole set of policies, people, processes, and technologies that protect an organisation — not just the firewall. The CCNA blueprint buckets it under Domain 5.5 “Describe security program elements”, and the three elements tested most are the human side: user awareness, training, and physical access control. Technology controls (ACLs, AAA, port security) only work when the program around them makes people behave and keeps intruders physically out.
Think of the three elements as legs of a stool:
| Element | What it covers | You implement it with... |
|---|---|---|
| User awareness | Recognising phishing, social engineering, unsafe downloads | Posters, onboarding modules, simulated phishing |
| Training | Building skill: how to use MFA, handle passwords, report incidents | Role-based classes, tabletop drills, certifications |
| Physical access control | Restricting who can touch devices, cables, and server rooms | Badges, locks, cameras, server-room mantraps, asset tracking |
Notice what the program protects: the humans who misuse credentials and the physical spaces where the hardware lives. An attacker who cannot talk their way in and cannot open a door is reduced to the technical attacks the other lessons in this week stop.
User awareness and training
User awareness is about recognising the threat; training is about doing the right thing. The distinction matters on the exam and in an SOC: awareness tells a user that “your account has been locked, click here” is a phishing lure; training teaches them to report it and to verify through a separate channel. Together they are the defence against social engineering — the attacker targeting the person, not the packet.
An effective programme is continuous and measured:
- Onboarding: security basics before any access is granted.
- Ongoing phishing simulation: safe, tracked tests that improve recognition rates.
- Clear reporting paths: one button/channel to report a suspicious email or device.
- Compliance and review: policies reviewed at least annually and after incidents.
Physical access control
Physical access control is the outermost layer: it decides who may physically reach the devices, cables, and facilities where the network runs. Logical measures like SSH and AAA assume the attacker has no console cable; physical controls are what guarantee that assumption:
- Badges / tailgating control for building and server-room entry (including mantraps in high-security areas).
- Locked racks and cable management so nobody can unplug a switch or tap a wall port.
- Cameras and access logs for auditing who entered when.
- Device accountability: tracking laptops and tokening lost/stolen assets, since a stolen device is a dual attack surface (data + credentials).
Physical and logical combine here: port security and 802.1X (Lesson 9) are the logical wall behind the physical door. A visitor who slips past the badge turnstile still faces a port that blocks their device.
WLAN security: open, WPA, WPA2, WPA3
Wireless traffic flies through the air, so authentication and encryption are not optional — they are the medium itself. The history of Wi-Fi security is a line of standards, and the exam expects you to order them and know what each fixed:
| Standard | Status | Encryption | What it introduced |
|---|---|---|---|
| Open | Guest/hotspot only | None | Everything is readable; never use for private data |
| WEP | Deprecated | RC4 (broken) | First attempt; cracked in minutes — never use |
| WPA | Legacy only | TKIP/RC4 | Bridged WEP’s flaws with frequent key rotation |
| WPA2 | Widely deployed | AES-CCMP | Modern robust encryption under CCMP |
| WPA3 | Current generation | AES-GCMP + SAE handshake | Stronger handshake, forward secrecy, easy connect |
Two facts to tattoo into memory: WEP and WPA/TKIP are broken and must not be used, and the exam’s security baseline for modern Wi-Fi is WPA2 with AES-CCMP, evolving to WPA3 with SAE.
Personal (PSK) vs enterprise (802.1X/EAP)
WPA2 and WPA3 each come in two flavours, and the difference is who shares the secret:
- Personal (PSK) — one pre-shared passphrase for the whole network. Every client uses the same key. Simple for home and small offices, but the key is hardcoded into every device, so it cannot tell one user from another and a leaked passphrase lets anyone join.
- Enterprise (802.1X/EAP) — each client authenticates individually against a RADIUS server using EAP over 802.1X. Every user gets their own credentials or certificate, and the access point (as authenticator) grants or denies per device. This is why WPA2-Enterprise and WPA3-Enterprise are the standard for any organisation that cares who is on the Wi-Fi.
The EAP back-and-forth is the same machinery from Lesson 9’s 802.1X: the supplicant (the Wi-Fi client) speaks to the authenticator (the access point), which forwards to the authentication server (RADIUS). A successful exchange opens the port; a failure leaves the client in the blocked/guest state.
AES-CCMP and the TKIP fall to history
Encryption in WPA2 is AES-CCMP: AES (Advanced Encryption Standard) used in a mode called CCMP (Counter Mode with CBC-MAC), which separately provides confidentiality (the counter-mode encryption) and integrity/authentication (the CBC-MAC message authentication code) on every frame. It is fast, hardware-accelerated, and considered secure.
TKIP (Temporal Key Integrity Protocol) grew from WPA’s attempt to patch WEP by rotating RC4 keys, and it was a bridge technology, not a destination. Its cipher and key management have known weaknesses, so TKIP is deprecated: modern Wi-Fi drops the option, and any exam answer recommending TKIP for security is wrong by construction.
One extra step for WPA3: it moves to AES-GCMP (Galois/Counter Mode with its own authentication), but the exam cares less about the new acronym than about the pair of ideas that follow: WPA3 uses the stronger SAE handshake and keeps forward secrecy even on the personal network.
SAE: the WPA3 handshake
WPA2-Personal’s 4-way handshake has a known weakness: an attacker who captures the handshake can offline-brute-force the passphrase, then decrypt historical traffic captured earlier. SAE (Simultaneous Authentication of Equals) replaces that negotiation in WPA3. Each side proves knowledge of the shared passphrase through a cryptographic exchange that:
- prevents offline dictionary attacks (each guess must be tried live with the other party);
- provides forward secrecy (even a captured session cannot be decrypted later if the passphrase is compromised);
- resists dictionary guessing sent by anyone in radio range, which used to be trivially fast against WPA2-PSK captures.
Choosing the right protection
Putting the whole picture together, a defensible choice flows like this:
- Public hotspot / random guests? Open network, isolated from private VLANs, never carrying sensitive traffic.
- Home or small office? WPA2-PSK with a long passphrase, upgraded to WPA3-SAE when the hardware supports it — the personal model is cheap and fine at this scale.
- Enterprise with named users and audit needs? 802.1X/EAP with RADIUS (WPA2- or WPA3-Enterprise), so every device authenticates individually and can be revoked.
- Whatever the flavour, AES only. Disable WEP and TKIP everywhere; they exist to be replaced, not retained for compatibility.
The vocabulary you need
Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.
Review
Check what you have learned with these review questions.
Sources & references
- Cisco. CCNA (200-301) Exam Topics. cisco.com.
- IETF. Request for Comments (RFCs). rfc-editor.org.
- IANA. Internet Assigned Numbers Authority registries. iana.org.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.