Across WEP, WPA, WPA2 and WPA3, what did each Wi-Fi security generation fix, and which should a WLAN still offer?
answer
- four rungs, each patching the last
- a firmware stopgap on old hardware
- AES arrives with full 802.11i
- passphrase guessing and management frames
basics
~20 sWEP used one static RC4 key; WPA's TKIP retrofitted per-packet keys and integrity onto that hardware; WPA2 made AES-based CCMP the baseline; WPA3 adds SAE, required PMF and a 192-bit mode. Offer WPA3, WPA2 only for stragglers.
solid answer
~40 sWEP, from the original 802.11 standard, encrypted with RC4 under a static shared key and had no key management. WPA, published by the Wi-Fi Alliance in 2002 as a subset of draft 802.11i, kept RC4 so existing hardware could take a firmware upgrade, but TKIP added per-packet keys, an integrity check, replay protection and fresh session keys from the four-way handshake. WPA2 certifies the full 802.11i-2004 amendment, with AES-based `CCMP` as the mandatory cipher. WPA3 keeps that foundation and changes authentication and management: `SAE` replaces the pre-shared key in Personal, Protected Management Frames are required, and Enterprise gains a 192-bit mode with `GCMP-256`. Today a WLAN offers WPA3, keeps WPA2 only for devices that cannot do better, and offers neither WEP nor TKIP.
go deeper
Recall the order WEP, WPA, WPA2, WPA3 and one fix per step: static key, firmware patch, AES, passphrase-guessing protection. Say plainly that WEP and TKIP are retired.
Explain why WPA kept RC4 (existing hardware), why WPA2 needed new hardware (AES), and that WPA3 keeps the RSN element, the four-way handshake and, in Personal, CCMP while changing authentication and requiring PMF.
Show you know which rung a real fleet is stuck on and why: devices that cannot do CCMP, clients without SAE, and the certification facts that tell you what new equipment will support.
Frame the ladder as a retirement schedule: each rung you still admit sets the floor for everyone on that SSID, and the decision is what replacement cost the business accepts to raise it.
## The four rungs at a glance Wi-Fi security has been rebuilt three times since the original 802.11 standard. Each generation is best remembered by the one problem it set out to fix. **WEP**, **WPA**, **WPA2** and **WPA3** are names the **Wi-Fi Alliance** gives to what it certifies; the mechanisms underneath are defined by **IEEE 802.11** amendments. | Generation | Data protection | How keys are established | What it fixed | |---|---|---|---| | WEP (original 802.11) | RC4 under a static 40- or 104-bit shared key | Typed in by hand; static WEP had no key management | Nothing before it: the first attempt at link encryption | | WPA (Wi-Fi Alliance, 2002) | TKIP: still RC4, with per-packet keys, an integrity check and replay protection | Four-way handshake from a PSK or 802.1X | WEP's static key and weak integrity, on hardware already in the field | | WPA2 (certifies 802.11i-2004) | `CCMP`, built on AES | Same four-way handshake, PSK or 802.1X | Replaced RC4 with an AES-based cipher as the mandatory baseline | | WPA3 | `CCMP` in Personal; `GCMP-256` in the 192-bit Enterprise mode | `SAE` replaces the PSK in Personal; PMF required | Offline guessing of shared passphrases, unprotected management frames, a higher-strength option | ## What each step fixed - **WEP** encrypted frames with **RC4** under a key that every station shared and that rarely changed. With no key management, one key protected all traffic for months, and its integrity check could not reliably detect tampering. It is retired; its own failure modes are covered with WEP itself. - **WPA** was published by the Wi-Fi Alliance in October 2002 as a subset of the then-draft 802.11i, because the finished amendment needed AES and most deployed hardware could not run it. Its cipher, **TKIP**, kept RC4 so that existing access points and adapters could be fixed by a **firmware upgrade**, and added a fresh key per packet, a message integrity check, a sequence counter against replay and per-session keys from the four-way handshake. It was always a stopgap; NIST SP 800-97 already judged TKIP unsuitable for high-assurance environments. - **WPA2** certifies the full **802.11i-2004** amendment, the Robust Security Network (RSN). Its cipher, **CCMP**, uses AES and is mandatory for any device claiming RSN compliance, while TKIP became optional. The price was hardware: many older devices could not run AES and had to be replaced. - **WPA3** keeps the RSN foundation and the four-way handshake, and changes what sits around them. **SAE** replaces the pre-shared key in Personal mode, so a recorded connection gives an eavesdropper nothing to test passphrase guesses against offline. **Protected Management Frames (PMF)** become required on WPA3 networks. Enterprise gains a **192-bit mode** with `GCMP-256`. ## What did not change Two things carry over and are easy to forget in an interview: 1. **WPA2 and WPA3 share the RSN framework.** A WPA3 network still advertises an RSN element, still runs the four-way handshake after authentication, and in Personal mode still protects data frames with CCMP. hostapd, the open-source reference implementation, configures WPA3 with the same `wpa=2` (RSN) bit as WPA2 and changes only the key management, for example `wpa_key_mgmt=SAE`. 2. **The labels are certifications, not amendments.** The Wi-Fi Alliance certifies WPA, WPA2 and WPA3; IEEE defines the mechanisms, such as 802.11i-2004 for RSN and CCMP and 802.11w-2009 for management frame protection. "WPA3 is part of 802.11ax" mixes the two. ## Where the industry stands now The Wi-Fi Alliance states that **WPA3 is mandatory for Wi-Fi CERTIFIED devices** and that **PMF is required for all new certified devices**. Implementations are retiring the oldest rungs: hostapd 2.10 (2022) removed WEP from its default build and added a build option that removes TKIP. The 6 GHz band admits neither: only RSN with PMF required. ## What a WLAN should offer today 1. **WPA3** (SAE for Personal, WPA3-Enterprise for 802.1X) on every SSID whose clients support it, and on 6 GHz only WPA3 or Wi-Fi Enhanced Open. 2. **WPA2 with CCMP**, ideally with PMF, only for the devices that cannot yet do WPA3, and only for as long as those devices remain. 3. **Never WEP or TKIP**, including TKIP hidden inside a WPA/WPA2 mixed-mode SSID, where it becomes the group cipher for every client. The short version for an interview is one line per rung: WEP had a static key, WPA patched it in firmware, WPA2 brought AES, WPA3 fixed passphrase guessing and protected the management frames.
- Does WPA3-Personal replace AES-CCMP with a new cipher?No. WPA3-Personal changes how the pairwise master key is established, with SAE instead of a key derived directly from the passphrase, and it requires PMF. Its data frames are normally still protected by AES-CCMP, the WPA2 cipher. `GCMP-256` is mandatory in WPA3-Enterprise's 192-bit mode and is offered alongside SAE by newer equipment, but it is not what defines WPA3-Personal.
- Is WPA2 still acceptable on a network built today?As a fallback, yes: WPA2 with CCMP has no retired cipher in it, and many deployed clients still cannot do WPA3. It should be offered only where such clients exist, with PMF enabled where they tolerate it, and it cannot follow them onto 6 GHz, which refuses the PSK method and requires PMF. The default target for every new SSID is WPA3.
- Which body defines WPA2 and WPA3: IEEE or the Wi-Fi Alliance?The Wi-Fi Alliance. WPA, WPA2 and WPA3 are its certification programmes, which test that products interoperate. The mechanisms they test are IEEE's: 802.11i-2004 defines the Robust Security Network and CCMP that WPA2 certifies, and 802.11w-2009 defines management frame protection, which WPA3 requires.
- WPA3 is a new IEEE amendment that replaced 802.11i.
- WPA3 drops the four-way handshake entirely.
- WPA3-Personal encrypts every data frame with GCMP-256.
- TKIP's per-packet keys make WPA/WPA2 mixed mode acceptable today.
- WEP with a 104-bit key is an acceptable fallback for old devices.
Assumes Wi-Fi Alliance programmes as of Wi-Fi 7 (2024): WPA3 mandatory for certified devices, PMF required for new certified devices; hostapd removed WEP from its default build in 2.10 (2022).