On a WPA2 network, what does the "AES" encryption setting actually refer to, and what does it protect in each data frame?
answer
- a mode, not just a cipher
- Counter Mode with CBC-MAC Protocol
- header plus MIC around the body
- addresses stay readable
basics
~20 sIn WPA2, "AES" means CCMP: AES in CCM mode with a 128-bit per-session temporal key. It encrypts each data frame's body and adds an 8-octet MIC that detects tampering, while the MAC header travels in the clear.
solid answer
~40 s"AES" in a WPA2 setup is shorthand for **CCMP**, the Counter Mode with CBC-MAC Protocol from 802.11i-2004. It runs AES in CCM mode with a 128-bit temporal key: counter mode encrypts the frame body (the IP packet and everything above it), and CBC-MAC produces an 8-octet MIC over the body and most of the MAC header, so a modified frame is dropped. An 8-octet CCMP header carries a 48-bit packet number, and the receiver rejects any frame whose number is not higher than the last one it accepted, which stops replays. What it does not hide: MAC addresses, frame sizes and timing, and management frames unless Protected Management Frames is negotiated. The label "WPA2-TKIP" names the retired RC4-based stopgap that CCMP replaced; in hostapd the setting to write is `rsn_pairwise=CCMP`.
go deeper
Recall that WPA2's AES is CCMP, that it uses a 128-bit key, and that it both encrypts the frame body and adds a MIC. Say plainly that MAC addresses stay visible.
Explain the frame layout: MAC header, 8-octet CCMP header with packet number and Key ID, encrypted body, 8-octet MIC. Name the RSN element's pairwise suite as the place the cipher is announced.
Show you verify rather than trust labels: read the RSN element, set rsn_pairwise explicitly in hostapd, and know which header fields and frame types CCMP leaves unprotected.
Frame the answer as a trust boundary: CCMP protects data frames against outsiders on the link, while admission, management-frame protection and key distribution are separate controls a security standard must also require.
## What "AES" names in a WPA2 configuration WPA2 is the Wi-Fi Alliance certification built on the IEEE **802.11i-2004** amendment, which defined the **Robust Security Network (RSN)**. Its data-protection cipher suite is **CCMP** — the *Counter Mode with CBC-MAC Protocol* — which runs the **AES** block cipher in **CCM mode** (RFC 3610, NIST SP 800-38C). When a router or a controller offers "WPA2-AES", it means CCMP. "WPA2-TKIP" names the Temporal Key Integrity Protocol, an RC4-based stopgap designed to run on WEP-era hardware; it is retired, and CCMP is what replaced it as the baseline. CCMP keys AES with a **128-bit temporal key (TK)**. Each associated client gets its own pairwise temporal key for unicast traffic, and the access point shares a group temporal key with all associated clients for broadcast and multicast traffic. Where those keys come from is the job of the four-way handshake, covered separately; for this question it is enough that the key is per session, derived by the devices, and never typed by anyone. ## What CCMP does to each data frame For every protected data frame — strictly, every MPDU, the unit the radio actually transmits — CCMP: - **inserts an 8-octet CCMP header** right after the 802.11 MAC header, carrying a 48-bit **packet number (PN)** and a **Key ID** that tells the receiver which installed key protected the frame; - **encrypts the frame body** — the LLC/SNAP header, the IP header, the transport ports and the application data — with AES in counter mode; - **appends an 8-octet MIC** (message integrity code), computed with AES-CBC-MAC over the plaintext body and most of the MAC header, so any modification is detected and the frame is discarded; - **sets the Protected Frame bit** in the Frame Control field so the receiver knows the body must be decrypted. | Part of the frame | Encrypted? | Covered by the MIC? | |---|---|---| | MAC header (addresses, most Frame Control bits) | No | Mostly, as additional authenticated data | | CCMP header (PN, Key ID) | No | The PN is bound in through the nonce | | Frame body (IP packet and above) | Yes | Yes | | MIC | Yes, with the keystream | It is the check itself | The packet number also provides **replay protection**: the receiver discards any frame whose PN is not higher than the last one it accepted for that key. CCMP therefore delivers three properties for data frames — confidentiality, integrity and freshness — with one key and one AES engine. ## What CCMP does not hide or cover "The Wi-Fi is encrypted" overstates what CCMP does. With CCMP in force: - the **MAC addresses** of sender and receiver, the BSSID, frame lengths and timing remain visible to anyone in radio range; - a few header fields are deliberately left out of the MIC — the Duration/ID field, and Frame Control bits such as Retry that can legitimately differ on a retransmission; - **management frames** (beacons, probe responses, deauthentication) are not protected by CCMP on a WPA2 network unless Protected Management Frames (802.11w) is negotiated, which is a separate subject; - **who is admitted** is not CCMP's decision at all: that is authentication, Personal or Enterprise, and the cipher only protects the link that authentication set up. ## Checking what is in force A reviewer or an engineer can confirm the cipher without trusting a product label: 1. Read the **RSN element** (element ID 48) in the access point's beacons or probe responses. Its pairwise cipher list holds suite selectors: `00-0F-AC:4` is CCMP, and `00-0F-AC:2` would mean TKIP is still offered. 2. Read the configuration. In hostapd, the open-source reference implementation, the WPA2 pairwise cipher is `rsn_pairwise=CCMP`. Write it explicitly: when it is unset, hostapd copies `wpa_pairwise`, whose default is TKIP unless hostapd was built with `CONFIG_NO_TKIP`. 3. Read association failures. A client that requests a pairwise cipher the access point does not offer is refused with status code 42, invalid pairwise cipher. ## Why interviewers ask it this way The question checks whether a candidate can move past "WPA2 uses AES" to what AES is doing: a **mode** (CCM), a **key size** (128 bits), a **per-frame header and MIC**, and a **counter against replays**. A strong answer names CCMP, says it gives data frames confidentiality, integrity and replay protection, and is honest that the MAC header, management frames and client admission are separate stories. A weak answer stops at "AES is strong encryption", which says nothing about what a single frame on the air actually carries.
- Does CCMP protect broadcast and multicast data frames as well as unicast ones?Yes. Unicast frames are protected with each client's own pairwise temporal key, and broadcast and multicast frames from the access point with the group temporal key that every associated client holds. Both use CCMP when CCMP is the negotiated cipher, and each key has its own packet numbers, so replay protection applies to group traffic too. The group key is replaced periodically by the access point.
- Is CCMP's 128-bit key weaker than the 256-bit keys some newer cipher suites use?Not in any practical sense: NIST SP 800-97 puts CCMP's key space at 2^128, far beyond exhaustive search. CCMP-256 and GCMP-256 exist for policies that demand a higher security level, such as WPA3-Enterprise's 192-bit mode, and they also lengthen the MIC to 16 octets. On an ordinary WPA2 network the real risks sit in how keys are shared and managed, not in AES key length.
- What happens to a CCMP-protected frame whose MIC check fails at the receiver?It is discarded. CCM releases no plaintext when the MIC does not verify, so nothing reaches higher layers and the frame's packet number is never recorded. TKIP had countermeasures that deauthenticated stations after repeated MIC failures (reason code 14); CCMP has no such mechanism, and TKIP itself is retired in favour of CCMP.
- WPA2-AES encrypts the whole frame, including the MAC addresses.
- The WPA2 passphrase itself is the AES key that encrypts each frame.
- CCMP only encrypts; integrity comes from the frame check sequence.
- WPA2-AES and WPA2-TKIP are the same protocol with different key lengths.
- WPA2's CCMP also protects beacons and deauthentication frames by default.