WPA2 vs WPA3: AES, SAE, and What Actually Changed

WPA2 (Wi-Fi Protected Access 2) encrypts wireless traffic with AES-CCMP using a 128-bit key, and in Personal mode it authenticates devices through a four-way handshake based on a pre-shared key. WPA3 keeps AES but replaces that handshake with Simultaneous Authentication of Equals (SAE), which blocks offline dictionary attacks against the passphrase, adds forward secrecy, and makes Protected Management Frames mandatory. When you set up a wireless network today, WPA3 is the strongest option you can select; WPA2 with AES is the acceptable fallback for older devices.

What WPA actually is

WPA stands for Wi-Fi Protected Access — a family of wireless security certifications from the Wi-Fi Alliance that define how a client and an access point authenticate each other and encrypt the traffic between them. WPA2, released in 2004, became the long-running standard, and WPA3, released in 2018, is its successor. On a small office/home office (SOHO) router, these appear as options in the wireless security dropdown, often alongside “mixed” or “transition” modes that accept both — picking the strongest supported mode is one piece of broader SOHO router hardening.

Two things happen every time a laptop or phone joins a protected network: authentication (proving the device is allowed on, usually by knowing the passphrase) and encryption (scrambling the traffic so nearby listeners cannot read it). WPA2 and WPA3 differ far more in the first step than the second.

Encryption: AES-CCMP in both, stronger options in WPA3

WPA2 encrypts traffic with AES (Advanced Encryption Standard) using CCMP — Counter Mode with Cipher Block Chaining Message Authentication Code Protocol — with a 128-bit key. That answers a question technicians get surprisingly often: the standard AES key length in WPA2 is 128 bits, and AES-CCMP is the protocol securing the traffic. This replaced the older TKIP cipher used by the original WPA, which is covered separately in WEP, WPA/TKIP, and WPS.

WPA3 keeps AES as the encryption workhorse but raises the ceiling. WPA3-Enterprise offers an optional 192-bit security mode built on a stricter cryptographic suite (GCMP-256 for encryption). When a client’s requirement is the highest available Wi-Fi cryptographic strength — government work, defense contractors, regulated environments — the answer is WPA3-Enterprise in 192-bit mode. No Personal-mode configuration reaches that level.

Authentication: the four-way handshake vs SAE

Here is where WPA3 earns its existence. In WPA2-Personal, every device shares one passphrase, and joining the network runs a four-way handshake derived from that pre-shared key (PSK). The weakness: an attacker who captures a single handshake — trivially done with a laptop parked nearby — can take the capture home and run an offline dictionary attack, testing millions of candidate passphrases per second against it with no further contact with the network. A weak or common passphrase falls quickly.

WPA3-Personal replaces the PSK exchange with Simultaneous Authentication of Equals. SAE is a password-authenticated key exchange (based on the “Dragonfly” handshake) in which both sides prove knowledge of the passphrase without ever transmitting material an attacker can grind against offline. Each guess at the password requires a live, interactive exchange with the access point — so an attacker gets one guess per attempt, at network speed, where the router can throttle or lock them out. That single change is the improvement SAE provides: it converts a capture-once, crack-anywhere attack into a slow online guessing game. It is also why upgrading an office from WPA2-Personal to WPA3-Personal is the correct move when the goal is protection against offline dictionary attacks and the client devices are recent enough to support it.

SAE brings a second benefit: forward secrecy. Each session negotiates fresh, unique encryption keys. If the Wi-Fi password is compromised next month, traffic an attacker recorded last month still cannot be decrypted — the recorded sessions were protected by keys that no longer exist and cannot be re-derived from the passphrase. WPA2 has no such property; a leaked passphrase plus a captured handshake unlocks previously recorded traffic.

Protected Management Frames: stopping deauth attacks

Wireless management frames — the housekeeping messages that tell a client to disconnect (deauthentication) or leave the association (disassociation) — were unauthenticated in the original WPA2 standard. Anyone with a cheap adapter could forge them, repeatedly kicking every client off a network. Attackers use this both as denial of service and as a setup step: knock a victim off the legitimate network so they reconnect to a rogue access point — the evil twin setup — or force handshakes to capture.

WPA3 makes Protected Management Frames (PMF, standardized as 802.11w) mandatory. With PMF, deauthentication and disassociation frames are cryptographically protected, so a client ignores forged ones. If a site suffers repeated deauth attacks, the WPA3 feature that directly addresses it is mandatory PMF — WPA2 networks can support 802.11w optionally, but many client devices never negotiated it.

Personal vs Enterprise

The Personal/Enterprise split exists in both generations and is a separate axis from WPA2-vs-WPA3. Personal mode uses one shared passphrase for everyone. Enterprise mode uses 802.1X authentication: each user or device presents individual credentials (username/password or a certificate) that are validated by a RADIUS (Remote Authentication Dial-In User Service) server. That is the primary difference — shared passphrase versus per-user authentication against a central server. Enterprise mode means you can revoke one employee’s access without re-keying every device in the building, and there is no single passphrase to leak on a sticky note. The client-side join experience — credential prompts and certificate warnings — is covered in Windows network profiles and client connections.

WPA2 vs WPA3 at a glance

Feature	WPA2	WPA3
Encryption	AES-CCMP (128-bit)	AES; up to 192-bit suite in Enterprise mode
Personal-mode handshake	Four-way handshake from pre-shared key	SAE (Simultaneous Authentication of Equals)
Offline dictionary attacks	Possible from one captured handshake	Blocked; guesses must be live and online
Forward secrecy	No	Yes — per-session keys
Protected Management Frames	Optional (802.11w)	Mandatory
Enterprise authentication	802.1X with RADIUS	802.1X with RADIUS, optional 192-bit mode

How the 220-1202 exam tests this

• A “strongest available option” scenario: a technician configures a new SOHO router or upgrades an office network, and the answer is WPA3 (or WPA3-Personal specifically when offline-dictionary-attack resistance is the stated concern).
• A feature-matching question: which WPA3 capability protects previously captured traffic after a later password compromise (forward secrecy), or which mandatory feature stops spoofed deauthentication frames (Protected Management Frames).
• A definitional check: what SAE improves over the WPA2 pre-shared key exchange, which cipher WPA2 uses (AES-CCMP), or the WPA2 AES key length (128-bit).
• A Personal-vs-Enterprise discriminator: an organization wants per-user credentials and central authentication — the answer involves 802.1X and a RADIUS server, not a stronger passphrase.

Feature-matching like this rewards repetition — see the same stems enough times in the practice exam bank and the WPA3 answers pick themselves.

Quick reference

• WPA = Wi-Fi Protected Access; WPA2 (2004) and WPA3 (2018) are Wi-Fi Alliance security generations.
• WPA2 encrypts with AES-CCMP using a 128-bit key.
• WPA3-Personal replaces the PSK four-way handshake with SAE, defeating offline dictionary attacks.
• WPA3 provides forward secrecy: past captured traffic stays safe even if the password later leaks.
• Protected Management Frames are mandatory in WPA3 and stop spoofed deauth/disassociation frames.
• WPA3-Enterprise 192-bit mode is the pick for “highest available cryptographic strength” requirements.
• Personal = one shared passphrase; Enterprise = per-user 802.1X authentication via a RADIUS server.
• On any new deployment, select WPA3 when the clients support it; WPA2-AES is the fallback, never TKIP or WEP.