Wi-Fi Security Protocols: WEP, WPA2, WPA3
Trace the evolution from the broken WEP standard through WPA2-PSK and Enterprise to the SAE handshake introduced in WPA3.
Wi-Fi Security Protocols: WEP, WPA2, WPA3 is a free Cloud & IT Cert Prep lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Cloud & IT Cert Prep learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Why Wireless Security Is Unique
Wireless networks broadcast signals through the air, crossing physical boundaries that wired networks respect. Anyone within range of a Wi-Fi signal can attempt to connect or capture traffic without physically accessing a building. This makes wireless inherently more exposed than wired networks. Security protocols — WEP, WPA, WPA2, and WPA3 — were developed progressively to address weaknesses found in their predecessors. Understanding this evolution is critical for the Security+ exam and for auditing real-world wireless environments.
WEP: The Broken Standard
WEP (Wired Equivalent Privacy) was the original 802.11 security standard introduced in 1997. It used a 40-bit (later 104-bit) key with the RC4 stream cipher and a 24-bit Initialization Vector (IV). The IV was far too small — with only 16 million possible values, IVs repeat rapidly on busy networks. Attackers could collect enough frames with repeated IVs to recover the secret key using statistical analysis. Tools like Aircrack-ng can crack WEP in minutes by capturing as few as 50,000 packets. WEP is completely broken and must never be used.
# WEP weaknesses:
# - 24-bit IV too small (reuses within hours)
# - RC4 key scheduling vulnerability
# - No MIC (message integrity check) — bit-flipping possible
# - No replay protection
#
# Cracking WEP with aircrack-ng:
# airodump-ng -c 6 --bssid AA:BB:CC:DD:EE:FF -w capture wlan0
# aircrack-ng capture-01.capWPA: Transitional Security
WPA (Wi-Fi Protected Access) was released in 2003 as an emergency fix while the 802.11i standard was being finalized. WPA introduced TKIP (Temporal Key Integrity Protocol), which added a per-packet key mixing function and a sequence counter to address WEP's IV reuse problem. It also added a Message Integrity Check (MIC) called Michael to detect packet tampering. However, TKIP still uses RC4 and inherits some weaknesses. WPA was designed to run on existing WEP hardware via firmware update and is now considered deprecated.
# WPA-TKIP improvements over WEP:
# + Per-packet key mixing (changes key per frame)
# + 48-bit IV (larger IV space)
# + Michael MIC (message integrity check)
# + Sequence counter (replay protection)
# - Still uses RC4 cipher (inherently weaker than AES)
# - TKIP has known theoretical attacks (ChopChop, Beck-Tews)WPA2: The Mainstream Standard
WPA2 implements the full IEEE 802.11i standard and replaced WPA as the mainstream Wi-Fi security protocol in 2004. The critical improvement is CCMP (Counter Mode with CBC-MAC Protocol), which uses AES instead of RC4. AES-CCMP provides both encryption and integrity protection using a 128-bit key. WPA2 has two modes: Personal (PSK) uses a shared passphrase and is suitable for homes and small offices, while Enterprise (802.1X/RADIUS) uses individual certificates or credentials per user for corporate environments.
# WPA2 comparison:
# WPA2-Personal (PSK):
# - Pre-Shared Key (passphrase)
# - All devices share the same key
# - Vulnerable to offline dictionary attacks on 4-way handshake
# WPA2-Enterprise (802.1X):
# - Each user authenticates individually
# - No shared secret; uses EAP + RADIUS
# - Much more secure for organizationsThe 4-Way Handshake and PMKID Attack
WPA2-PSK security depends on the 4-way handshake that occurs when a client connects. Both the AP and client prove they know the Pre-Shared Key by exchanging nonces and computing a Pairwise Transient Key (PTK). An attacker who captures this handshake can attempt an offline dictionary attack — testing millions of passwords — without interacting with the AP. The newer PMKID attack (2018) extracts a single PMKID frame from the first EAPOL message, removing the need to capture a full client authentication, making passive capture unnecessary for cracking WPA2-PSK.
# Capturing WPA2 4-way handshake:
# airodump-ng -c 6 --bssid AA:BB:CC:DD:EE:FF -w capture wlan0
# aireplay-ng --deauth 5 -a AA:BB:CC:DD:EE:FF wlan0
# aircrack-ng -w wordlist.txt capture-01.cap
# PMKID attack (no deauth needed):
# hcxdumptool -i wlan0 -o pmkid.pcapng --enable_status=1
# hcxpcapngtool pmkid.pcapng -o hash.txt
# hashcat -m 22000 hash.txt wordlist.txtWPA3: The Modern Standard
WPA3 was introduced in 2018 to address WPA2's weaknesses. Its most important improvement is replacing the PSK 4-way handshake with SAE (Simultaneous Authentication of Equals), also called Dragonfly. SAE provides forward secrecy — captured traffic cannot be decrypted retroactively even if the password is later compromised — and prevents offline dictionary attacks because each login attempt requires interacting with the AP. WPA3-Enterprise mandates 192-bit security suite for sensitive environments. WPA3 also introduces Enhanced Open (OWE) that encrypts open networks without requiring a password.
# WPA3 improvements over WPA2:
# + SAE replaces PSK 4-way handshake
# + Forward secrecy (unique session keys per connection)
# + No offline dictionary attacks (active interaction required)
# + 192-bit mode for WPA3-Enterprise (CNSA suite)
# + OWE encrypts open/captive-portal networks
# + PMF (Protected Management Frames) mandatoryProtected Management Frames (PMF)
PMF (Protected Management Frames), defined in 802.11w, provides integrity protection for management frames like deauthentication and disassociation. Without PMF, these frames are unauthenticated and can be forged by anyone within radio range, enabling deauthentication attacks that kick clients off a network. PMF is optional in WPA2 but mandatory in WPA3. Enabling PMF in WPA2 networks blocks most deauth-based attacks, including the prerequisite step for many evil-twin and handshake capture attacks.
# Hostapd configuration with PMF:
# /etc/hostapd/hostapd.conf
# wpa=2
# wpa_key_mgmt=WPA-PSK
# ieee80211w=2 <- 0=disabled, 1=optional, 2=required
# wpa_pairwise=CCMP
# PMF=2 (required) blocks deauthentication spoofing attacksWPS Vulnerabilities
WPS (Wi-Fi Protected Setup) was designed to simplify connecting devices to WPA2 networks using an 8-digit PIN or push-button. The PIN method is critically flawed: the 8-digit PIN is actually two independent 4-digit PINs validated separately, reducing the keyspace from 100 million to 11,000 combinations. The Reaver and Bully tools can brute-force a WPS PIN in hours. Even after locking out, some APs reset the lockout timer. The PIN-based WPS should be disabled entirely; push-button WPS has a narrower attack window but still poses risk.
# WPS PIN brute-force:
# reaver -i wlan0mon -b AA:BB:CC:DD:EE:FF -vv
# Disable WPS in router admin interface
# OR verify via:
nmap -p 80 --script http-wps-detect 192.168.1.1
# WPS enabled and PIN mode = HIGH RISK, disable immediatelyWireless Encryption Key Selection
Choosing strong encryption for your wireless network involves selecting the right protocol and configuration. The recommended hierarchy from strongest to weakest is: WPA3-Enterprise > WPA3-Personal > WPA2-Enterprise > WPA2-Personal. For WPA2/3-Personal, use a passphrase of at least 20 random characters to resist offline dictionary attacks. Avoid TKIP entirely — use CCMP/AES only. Configure cipher suites explicitly rather than allowing mixed mode, which may negotiate down to weaker ciphers for backwards compatibility with older devices.
# Recommended hostapd/wpa_supplicant settings:
# Protocol: WPA3 (wpa=3) or WPA2 (wpa=2)
# Key mgmt: WPA-PSK-SHA256 or SAE (WPA3)
# Pairwise: CCMP (AES) only
# Avoid: TKIP, WEP, mixed WPA+WPA2
# Passphrase: >= 20 random characters for PSK
# WPS: DisabledComparing Standards for the Exam
The Security+ exam frequently tests your ability to compare wireless protocols. Key differentiators: WEP uses RC4 with a broken short IV — always the wrong choice. WPA/TKIP is deprecated and also uses RC4. WPA2/CCMP uses AES and is the current minimum acceptable standard. WPA3/SAE adds forward secrecy and eliminates offline dictionary attacks. Enterprise mode (802.1X/RADIUS) is always more secure than Personal/PSK mode for organizations. Memorize these distinctions and why each was introduced.
Regulatory and Compliance Considerations
Many compliance frameworks mandate specific wireless security controls. PCI-DSS requires WPA2 or higher with AES encryption for any wireless network in scope for cardholder data. Organizations must also inventory all wireless access points quarterly and test for rogue APs. HIPAA requires encryption of wireless data containing PHI. Auditors look for network documentation, encryption standards, rogue AP detection programs, and periodic wireless vulnerability assessments. Failing to upgrade from WEP or WPA/TKIP in a PCI environment can result in significant penalties.
Quick Check
Test your understanding of CompTIA Security+ (SY0-701) concepts from this lesson.
Lesson Recap
In this lesson you learned: WEP is completely broken due to its short IV and RC4 weaknesses and must never be used, WPA2/CCMP uses AES but WPA2-Personal is vulnerable to offline dictionary attacks against captured 4-way handshakes, and WPA3/SAE provides forward secrecy and prevents offline cracking by requiring active AP interaction. Next up we explore specific wireless attacks including evil twin and deauthentication techniques.
Frequently asked questions
Is the “Wi-Fi Security Protocols: WEP, WPA2, WPA3” lesson free?
Yes — the full text of “Wi-Fi Security Protocols: WEP, WPA2, WPA3” is free to read here on the web, and the Cloud & IT Cert Prep course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Cloud & IT Cert Prep course, upgrade to CoddyKit PRO.
What will I learn in “Wi-Fi Security Protocols: WEP, WPA2, WPA3”?
Trace the evolution from the broken WEP standard through WPA2-PSK and Enterprise to the SAE handshake introduced in WPA3. You practise Cloud & IT Cert Prep with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Cloud & IT Cert Prep?
No prior experience is required. Cloud & IT Cert Prep on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Wi-Fi Security Protocols: WEP, WPA2, WPA3” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Cloud & IT Cert Prep lesson?
Yes. Every Cloud & IT Cert Prep lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Wi-Fi Security Protocols: WEP, WPA2, WPA3
- Wireless Attacks: Evil Twin, Deauth, and Rogue AP
- Enterprise Wireless: 802.1X and RADIUS
- Bluetooth and IoT Wireless Threats