Unlike wired networks where physical access is required to intercept traffic, wireless networks broadcast signals through the air — available to anyone within range. Every device that can receive the signal can, in principle, attempt to read it. This makes encryption and authentication not optional add-ons but foundational requirements. This guide traces the evolution of wireless security protocols, the authentication models that back them, and the attacks that expose gaps in each layer.
The Shared Medium Problem
A wired network carries traffic through cables. To sniff that traffic, an attacker must gain physical access to the cable, the switch, or the device. The barrier is tangible.
A wireless network sends traffic as radio waves. Any receiver within range can detect those waves. Without encryption, every packet is visible to every listener — a persistent, passive attacker can silently collect everything.
This is the core problem that every wireless security standard tries to solve: how do you protect confidential data traveling over a medium that, by its nature, is shared with everyone nearby?
WIRED NETWORK WIRELESS NETWORK
┌──────┐ cable ┌──────┐ ┌──────┐ ~~~~~ ┌──────┐
│ Host │────────────│ Host │ │ Host │~~~~~~~~~│ Host │
└──────┘ └──────┘ └──────┘ └──────┘
~ ~ ~ ~
Any listener in range
receives these signals
Encryption is the primary answer: transform the data so that even if an attacker captures every packet, they cannot read what those packets contain without the key.
802.11 Standards: Frequency, Speed, and Generation
Before examining security protocols, it helps to understand that all Wi-Fi networks are built on the IEEE 802.11 family of standards. Each generation defines the radio frequency, maximum speed, and range used:
┌──────────────┬───────────────┬────────────────┬───────────────────┐
│ Standard │ Frequency │ Max Speed │ Common Name │
├──────────────┼───────────────┼────────────────┼───────────────────┤
│ 802.11a │ 5 GHz │ 54 Mbps │ Wi-Fi 1 (1999) │
│ 802.11b │ 2.4 GHz │ 11 Mbps │ Wi-Fi 2 (1999) │
│ 802.11g │ 2.4 GHz │ 54 Mbps │ Wi-Fi 3 (2003) │
│ 802.11n │ 2.4 / 5 GHz │ 600 Mbps │ Wi-Fi 4 (2009) │
│ 802.11ac │ 5 GHz │ ~3.5 Gbps │ Wi-Fi 5 (2013) │
│ 802.11ax │ 2.4 / 5 GHz │ ~9.6 Gbps │ Wi-Fi 6 (2019) │
└──────────────┴───────────────┴────────────────┴───────────────────┘
For the Security+ exam, knowing these standard names matters less than knowing the security protocols that operate on top of them — which are the same regardless of the 802.11 generation in use.
WEP: The Broken Foundation
WEP (Wired Equivalent Privacy) was the original wireless encryption standard, introduced in 1997 as part of 802.11. Its name was aspirational: the goal was to make wireless as safe as wired by making eavesdropping impractical.
The name turned out to be marketing, not fact.
How WEP Works
WEP uses the RC4 stream cipher combined with a static, manually configured key — typically 40 or 104 bits. To encrypt each packet, WEP appends a 24-bit IV (Initialization Vector) to the key and feeds the combined value into RC4 to produce a keystream. The keystream is XORed with the plaintext to produce the ciphertext.
┌───────────────┐ ┌─────────────────────────┐
│ Static Key │ │ IV (24-bit, in packet │
│ (40/104 bit) │──────────│ header — visible to │
└───────────────┘ │ any listener) │
│ └─────────────────────────┘
└──────────────────────────┐
▼
┌──────────────────┐
│ RC4 Keystream │
└────────┬─────────┘
│ XOR
┌────────▼─────────┐
│ Ciphertext │
└──────────────────┘
Why WEP Failed
The 24-bit IV space contains only 16,777,216 unique values. On a busy network, IVs repeat within hours — sometimes minutes. When two packets are encrypted with the same IV and key, an attacker can XOR the two ciphertexts together, canceling out the keystream and revealing relationships between the plaintexts. This is the IV collision attack.
Tools like Aircrack-ng can recover a WEP key passively in minutes by collecting enough packets with colliding IVs. WEP is not just weak — it is cryptographically broken. No configuration option makes it safe.
WEP should never be used. Any legacy device that supports only WEP should be replaced.
WPA: The Emergency Replacement
When WEP's vulnerabilities became undeniable, the Wi-Fi Alliance needed a rapid replacement that could run on existing hardware. The result was WPA (Wi-Fi Protected Access), introduced in 2003.
WPA replaced RC4's static-key approach with TKIP (Temporal Key Integrity Protocol). TKIP generates a unique encryption key for every packet using a per-packet key mixing function, making IV-collision attacks significantly harder. It also introduced Michael MIC (Message Integrity Check) to detect packet tampering.
WEP WPA / TKIP
┌──────────────────────┐ ┌──────────────────────┐
│ Static key + 24-bit │ │ Per-packet key mixing │
│ IV reused → broken │ │ 48-bit IV → harder │
└──────────────────────┘ │ Michael MIC added │
└──────────────────────┘
WPA was designed as a software upgrade for existing WEP hardware. It bought time, but it was never intended to be permanent. Cryptographic vulnerabilities were discovered in TKIP, and WPA is now deprecated and should not be used.
WPA2: The Current Standard
WPA2, ratified in 2004 and mandated for all Wi-Fi certified devices since 2006, replaced TKIP entirely with a cryptographically sound combination: AES and CCMP.
- AES (Advanced Encryption Standard) — the symmetric block cipher. AES replaced RC4 entirely. Where RC4 was a stream cipher with well-known weaknesses, AES is a block cipher that has withstood decades of cryptanalysis.
- CCMP (Counter Mode with Cipher Block Chaining Message Authentication Protocol) — the protocol that combines AES encryption with an integrity check. CCMP provides both confidentiality (nobody can read the traffic) and integrity (nobody can modify it without detection).
┌──────────────────────────────────────────────────────────┐
│ WPA2 │
│ │
│ Encryption: AES (block cipher, 128-bit key) │
│ Protocol: CCMP (confidentiality + integrity) │
│ │
│ Exam mnemonic: An Entertaining System = a CCoMPuter │
│ AES ────── CCMP │
└──────────────────────────────────────────────────────────┘
WPA2 is still widely deployed and, when configured correctly, provides strong security. Its primary practical vulnerability is against offline dictionary attacks on weak pre-shared keys — discussed below.
WPA3: The Modern Standard
WPA3, introduced in 2018, builds on WPA2 with a stronger cryptographic foundation and new features.
Encryption: AES and GCMP
WPA3 replaces CCMP with GCMP (Galois/Counter Mode Protocol). Like CCMP, GCMP provides both confidentiality and integrity — but GCMP is more efficient and supports larger key sizes (192-bit in WPA3-Enterprise).
┌──────────────────────────────────────────────────────────┐
│ WPA3 │
│ │
│ Encryption: AES (same cipher, stronger mode) │
│ Protocol: GCMP (replaces CCMP) │
│ │
│ Exam mnemonic: An Entertaining System = a Gaming CoMPuter│
│ AES ────── GCMP │
└──────────────────────────────────────────────────────────┘
SAE: Replacing the Pre-Shared Key Handshake
WPA2-Personal uses a 4-way handshake to derive session keys from the PSK. This handshake is transmitted over the air and can be captured. An attacker who captures the handshake can run an offline dictionary attack — trying millions of passwords per second without ever interacting with the network again.
WPA3-Personal replaces this with SAE (Simultaneous Authentication of Equals), also known as Dragonfly. SAE uses a zero-knowledge proof: the password is verified without ever transmitting anything that can be used to verify guesses offline. This eliminates the offline dictionary attack vector.
SAE also provides forward secrecy: each session generates a fresh key, so compromising one session's key does not expose past sessions.
WPA2 Handshake (offline attack possible)
─────────────────────────────────────────
Client ───── capture this ───── AP
(contains data needed
to verify PSK offline)
WPA3 / SAE (offline attack not possible)
─────────────────────────────────────────
Client ◀──── mutual zero-knowledge ────▶ AP
(no material usable offline)
OWE: Protecting Open Networks
WPA3 introduces OWE (Opportunistic Wireless Encryption), also called Enhanced Open. Open networks (coffee shops, airports) traditionally transmit all data in plaintext. OWE applies encryption transparently to open networks — no password is required to join, but traffic is still encrypted between each client and the access point. Clients cannot read each other's traffic even though there is no shared credential.
QR Code Joining
WPA3 supports joining a network by scanning a QR code through the DPP (Device Provisioning Protocol). The QR code encodes the network credentials and bootstraps the device's connection without manual password entry. This also enables IoT devices with no keyboard to join networks securely.
WPA Version Comparison
┌──────────┬──────────┬────────────┬─────────────────────────────────┐
│ Protocol │ Cipher │ Protocol │ Key Exchange │
├──────────┼──────────┼────────────┼─────────────────────────────────┤
│ WEP │ RC4 │ IV + CRC │ Static key — BROKEN │
│ WPA │ RC4 │ TKIP + MIC │ PSK (4-way) — deprecated │
│ WPA2 │ AES │ CCMP │ PSK (4-way) — offline attack │
│ WPA3 │ AES │ GCMP │ SAE (Dragonfly) — forward secret │
└──────────┴──────────┴────────────┴─────────────────────────────────┘
Exam shortcut: When given two of three — a protocol name (WPA2/WPA3), a cipher (AES), or a protocol (CCMP/GCMP) — you must supply the third.
- WPA2 + AES → CCMP
- WPA3 + AES → GCMP
- AES + CCMP → WPA2
- AES + GCMP → WPA3
Personal vs Enterprise: Authentication Models
Both WPA2 and WPA3 come in two authentication modes. Understanding the difference is critical for the exam and for real-world deployment.
Personal Mode: Pre-Shared Key
WPA2-Personal / WPA3-Personal authenticate using a PSK (Pre-Shared Key). Every device that joins the network uses the same passphrase. The PSK is configured on the access point and distributed manually to users.
HOME NETWORK (WPA2-Personal)
┌───────────────────────────────────────────────┐
│ All devices: same Wi-Fi password │
│ "What's the Wi-Fi password?" → PSK │
│ │
│ Simple to manage, no server required │
│ Cannot revoke access for one user │
│ Cannot trace traffic to a specific identity │
└───────────────────────────────────────────────┘
Personal mode is appropriate for home networks and small offices where accountability and individual revocation are not required. Its significant weakness is that all users share a single credential: if it leaks, all access must be reset.
Enterprise Mode: 802.1X and RADIUS
WPA2-Enterprise / WPA3-Enterprise replace the shared PSK with per-user authentication using 802.1X, which integrates with an authentication server — almost always RADIUS (Remote Authentication Dial-In User Service).
Each user provides their own credentials (username and password, or a certificate) when joining the network. The access point does not verify these credentials itself — it passes them to the RADIUS server, which makes the access decision.
ENTERPRISE NETWORK (WPA2-Enterprise)
┌─────────┐ credentials ┌─────────────┐ validate ┌──────────────┐
│ Client │──────────────────▶│ Access Point│───────────────▶│ RADIUS Server│
│ │ │ (Authenticat│ │ (Auth Server)│
│ │◀── grant/deny ───│ or) │◀── result ────│ │
└─────────┘ └─────────────┘ └──────────────┘
Each user authenticates with their own identity.
Access can be revoked per user without changing a shared password.
The underlying framework that carries credentials between the client and the authentication server is EAP (Extensible Authentication Protocol). EAP defines how credentials are formatted and verified. Common EAP types used with WPA-Enterprise include:
- EAP-TLS — mutual certificate authentication (strongest; both client and server present certificates)
- PEAP (Protected EAP) — wraps EAP in TLS, uses password authentication inside the tunnel
- EAP-TTLS — similar to PEAP, slightly more flexible
┌──────────────────────────────────────────────────────────────┐
│ 802.1X FRAMEWORK │
│ │
│ Supplicant (client) ── EAP ── Authenticator (AP) ── RADIUS │
│ │
│ EAP message types: │
│ ┌──────────┬──────────────────────────────────────────────┐ │
│ │ EAP-TLS │ Mutual certs — highest security │ │
│ │ PEAP │ Server cert + password inside TLS tunnel │ │
│ │ EAP-TTLS │ Server cert + flexible inner auth │ │
│ └──────────┴──────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────┘
Enterprise mode is the correct choice for any organization that needs:
- Individual user accountability
- Per-user access revocation (e.g., when an employee leaves)
- Integration with existing directory services (Active Directory, LDAP)
- Compliance with security policies requiring unique credentials
Network Identifiers: SSID, BSSID, and ESSID
Understanding these terms is important for both the exam and wireless attack scenarios.
- SSID (Service Set Identifier) — the human-readable name of the wireless network (e.g., "CorpNet"). An SSID can be broadcast (visible in scan lists) or hidden (requires knowing the name to connect).
- BSSID (Basic Service Set Identifier) — the MAC address of the access point radio. Uniquely identifies a specific physical AP.
- ESSID (Extended Service Set Identifier) — used when multiple APs share the same SSID, forming a single logical network across a campus. The ESSID is the shared network name; each AP has its own BSSID.
Hidden SSIDs are often presented as a security measure, but they provide negligible protection. When a client connects to a hidden SSID, the SSID appears in plaintext in the probe frames — any passive listener can learn it. Hidden SSIDs are a configuration inconvenience, not a security control.
MAC address filtering — allowing only specific MAC addresses to connect — is similarly weak. MAC addresses are transmitted in plaintext in 802.11 frames and can be spoofed trivially with any modern wireless adapter.
Wireless Attacks
Evil Twin (Rogue Access Point)
An evil twin attack places a rogue access point that mimics the SSID (and often the BSSID) of a legitimate AP. Clients connecting to the evil twin have their traffic routed through the attacker. The attacker can read unencrypted traffic, inject content, or capture credentials.
Legitimate AP: SSID="CorpNet" BSSID=AA:BB:CC:11:22:33
Evil Twin: SSID="CorpNet" BSSID=AA:BB:CC:44:55:66
Client connects to strongest signal — which the attacker controls.
Mitigations: use WPA2/WPA3-Enterprise with mutual certificate authentication (EAP-TLS), which requires the server to prove its identity — a rogue AP cannot present a valid certificate. Also use wireless intrusion detection systems (WIDS) to detect unexpected APs.
Deauthentication Attack
802.11 management frames are unauthenticated in WPA2 and earlier. An attacker can inject deauthentication frames spoofed from the AP's BSSID, forcing clients off the network. This is used as a step before an evil twin attack (to force clients to reconnect) or as a denial-of-service. WPA3 protects against this through PMF (Protected Management Frames), which authenticates management frames cryptographically.
Dictionary Attack on PSK (WPA2 Handshake Capture)
In WPA2-Personal, the 4-way handshake contains enough information to verify password guesses offline. An attacker uses deauthentication frames to force a client to reconnect, captures the handshake, and then runs an offline dictionary attack against it with tools like Hashcat or Aircrack-ng.
1. Attacker sends deauth → client disconnects
2. Client reconnects → 4-way handshake transmitted over air
3. Attacker captures handshake
4. Attacker runs offline dictionary attack (no network interaction needed)
5. If PSK is weak: cracked
WPA3-Personal eliminates this attack via SAE.
WPS PIN Attack
WPS (Wi-Fi Protected Setup) was introduced to simplify device joining via an 8-digit PIN. A design flaw in the WPS specification allowed the PIN to be brute-forced in at most ~11,000 attempts (due to the way the 8-digit PIN is verified in two halves). Tools like Reaver exploit this. WPS should be disabled on all production access points.
Wardriving
Wardriving is the practice of driving around with a wireless adapter and GPS to discover and map accessible wireless networks. It is used in reconnaissance to identify targets. The term comes from "war dialing" — systematically calling phone numbers to find modem connections.
Disassociation Attack
Similar to a deauthentication attack, a disassociation attack sends forged disassociation frames to disconnect clients. The effect and mitigations are the same as for deauthentication attacks — PMF (Protected Management Frames) is the defense.
WPS and Its Vulnerabilities
WPS (Wi-Fi Protected Setup) was designed to simplify adding devices to a network using a PIN or a push button. The security problems with the PIN method led to it being effectively abandoned:
WPS PIN Structure
┌───────────────────────────────────────────────────────┐
│ 8 digits total │
│ ┌─────────────────┬──────────────────────────────┐ │
│ │ First 4 digits │ Last 3 digits + checksum │ │
│ │ (verified │ (verified separately) │ │
│ │ independently) │ │ │
│ └─────────────────┴──────────────────────────────┘ │
│ │
│ Result: only 10^4 + 10^3 = 11,000 combinations │
│ (not 10^8 = 100,000,000 that 8 digits implies) │
└───────────────────────────────────────────────────────┘
Disable WPS on all access points. Even push-button WPS introduces physical security concerns.
Site Surveys and Heat Maps
Before deploying wireless in a professional environment, a site survey is performed to understand the physical radio environment:
Site Survey
A site survey involves physically traversing the space — typically with a laptop on a cart — while software records signal strength, channel utilization, interference sources, and coverage gaps at each position. The survey data is georeferenced (tied to the physical map of the space).
Site surveys answer:
- Where is coverage strong or weak?
- Where are dead zones?
- Where is interference occurring (from neighboring networks or non-Wi-Fi devices)?
- How many access points are needed and where should they be placed?
Heat Map
The output of a site survey is fed into software that generates a heat map — a visual overlay on the floor plan showing coverage intensity:
OFFICE FLOOR PLAN HEAT MAP
┌───────────────────────────────────────────┐
│░░░░░░░░░░░░░▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░│
│░░░░░░░░▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░│
│░░░░▓▓▓▓▓▓▓▓████████████████▓▓▓▓▓▓░░░░░░│
│░░▓▓▓▓▓▓▓▓████████[AP]████████▓▓▓▓▓▓░░░░│
│░░░▓▓▓▓▓▓▓▓████████████████▓▓▓▓▓▓░░░░░░░│
│░░░░░░▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░│
│░░░░░░░░░░░░░░▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░│
│ │
│ ████ Strong ▓▓▓▓ Moderate ░░░░ Weak/None│
└───────────────────────────────────────────┘
Heat maps reveal coverage gaps and overlap. Too much overlap wastes capacity and increases interference; too little leaves dead zones. The goal is uniform, overlapping coverage that provides seamless roaming without interference.
Passive vs Active Surveys
- Passive survey — the device listens and records all detected signals without associating to any network. Useful for measuring the existing radio environment.
- Active survey — the device associates with the network and measures actual throughput. Useful for validating real-world performance.
Wireless Network Modes
Infrastructure Mode
The standard deployment mode: clients connect through a central access point (AP) that connects to the wired network. All client-to-client traffic flows through the AP.
Ad-Hoc Mode (IBSS)
Independent Basic Service Set (IBSS) — clients communicate directly without an AP. Intended for temporary peer-to-peer connections. Ad-hoc networks cannot use WPA2-Enterprise (no AP to authenticate through) and represent a security risk if allowed on corporate networks.
Mesh Networks
Multiple APs communicate wirelessly with each other to form a mesh, extending coverage without wired backhaul at every node. WPA3's DPP (Device Provisioning Protocol) is particularly suited to mesh deployment.
Key Exam Reference
┌─────────────────────────────────────────────────────────────────┐
│ WIRELESS SECURITY QUICK REFERENCE │
├─────────────────────────────────────────────────────────────────┤
│ WEP │ RC4 + IV (24-bit) │ BROKEN — never use │
│ WPA │ RC4 + TKIP │ Deprecated — do not use │
│ WPA2 │ AES + CCMP │ Current standard │
│ WPA3 │ AES + GCMP │ Strongest; use when available │
├─────────────────────────────────────────────────────────────────┤
│ Personal │ PSK (shared passphrase) │ Home/small office │
│ Enterprise │ 802.1X + RADIUS + EAP │ Corporate │
├─────────────────────────────────────────────────────────────────┤
│ SAE (Dragonfly) │ WPA3-Personal key exchange (replaces 4-way) │
│ OWE │ WPA3 encryption for open networks │
│ PMF │ Protects management frames (deauth defense) │
│ WPS │ Insecure PIN setup — disable on all APs │
├─────────────────────────────────────────────────────────────────┤
│ Attack │ Target │ Defense │
│ Evil Twin │ No mutual auth │ EAP-TLS certs │
│ Deauth/Disassoc │ Unprotected mgmt │ PMF (WPA3) │
│ PSK Dict Attack │ Weak PSK + 4-way │ WPA3-Personal / SAE │
│ WPS PIN Brute Force │ WPS enabled │ Disable WPS │
└─────────────────────────────────────────────────────────────────┘
Related
- Wireless Attacks - rogue AP, Bluetooth and RFID attack techniques
- Network Attacks - MITM and sniffing over wireless links