IEEE 802.11i-2004, or 802.11i for short, is an amendment to the original IEEE 802.11, implemented as Wi-Fi Protected Access II. The draft standard was ratified on 24 June 2004. This standard specifies security mechanisms for wireless networks, replacing the short Authentication and privacy clause of the original standard with a detailed Security clause. In the process, the amendment deprecated broken Wired Equivalent Privacy, while it was later incorporated into the published IEEE 802.11-2007 standard.
Replacement of WEP
802.11i supersedes the previous security specification, Wired Equivalent Privacy, which was shown to have security vulnerabilities. Wi-Fi Protected Access had previously been introduced by the Wi-Fi Alliance as an intermediate solution to WEP insecurities. WPA implemented a subset of a draft of 802.11i. The Wi-Fi Alliance refers to their approved, interoperable implementation of the full 802.11i as WPA2, also called RSN. 802.11i makes use of the Advanced Encryption Standardblock cipher, whereas WEP and WPA use the RC4stream cipher.
Protocol operation
IEEE 802.11i enhances IEEE 802.11-1999 by providing a Robust Security Network with two new protocols: the four-way handshake and the group key handshake. These utilize the authentication services and port access control described in IEEE 802.1X to establish and change the appropriate cryptographic keys. The RSN is a security network that only allows the creation of robust security network associations, which are a type of association used by a pair of stations if the procedure to establish authentication or association between them includes the 4-Way Handshake. The standard also provides two RSNA data confidentiality and integrity protocols, TKIP and CCMP, with implementation of CCMP being mandatory since the confidentiality and integrity mechanisms of TKIP are not as robust as those of CCMP. The main purpose to implement TKIP was that the algorithm should be implementable within the capabilities of most of the old devices supporting only WEP. The initial authentication process is carried out either using a pre-shared key, or following an EAP exchange through 802.1X. This process ensures that the client station is authenticated with the access point. After the PSK or 802.1X authentication, a shared secret key is generated, called the Pairwise Master Key. In PSK authentication, the PMK is actually the PSK, which is typically derived from WiFi password by putting it through a key derivation function that use SHA-1 as the cryptographic hash function. If an 802.1X EAP exchange was carried out, the PMK is derived from the EAP parameters provided by the authentication server.
Four-way handshake
The four-way handshake is designed so that the access point and wireless client can independently prove to each other that they know the PSK/PMK, without ever disclosing the key. Instead of disclosing the key, the access point and client encrypt messages to each other—that can only be decrypted by using the PMK that they already share—and if decryption of the messages was successful, this proves knowledge of the PMK. The four-way handshake is critical for protection of the PMK from malicious access points—for example, an attacker's SSID impersonating a real access point—so that the client never has to tell the access point its PMK. The PMK is designed to last the entire session and should be exposed as little as possible; therefore, keys to encrypt the traffic need to be derived. A four-way handshake is used to establish another key called the Pairwise Transient Key. The PTK is generated by concatenating the following attributes: PMK, APnonce, STA nonce, AP MAC address, and STA MAC address. The product is then put through a pseudo-random function. The handshake also yields the GTK, used to decrypt multicast and broadcast traffic. The actual messages exchanged during the handshake are depicted in the figure and explained below :
The AP sends a nonce-value to the STA together with a Key Replay Counter, which is a number that is used to match each pair of messages sent, and discard replayed messages. The STA now has all the attributes to construct the PTK.
The STA sends its own nonce-value to the AP together with a Message Integrity Code, including authentication, which is really a Message Authentication and Integrity Code, and the Key Replay Counter which will be the same as Message 1, to allow AP to match the right Message 1.
The AP verifies Message 2, by checking MIC, RSN, ANonce and Key Replay Counter Field, and if valid constructs and sends the GTK with another MIC.
The STA verifies Message 3, by checking MIC and Key Replay Counter Field, and if valid sends a confirmation to the AP.
The Pairwise Transient Key is divided into five separate keys:
16 bytes of EAPOL-Key Confirmation Key – Used to compute MIC on WPA EAPOL Key message
16 bytes of EAPOL-Key Encryption Key – AP uses this key to encrypt additional data sent to the client
16 bytes of Temporal Key – Used to encrypt/decrypt Unicast data packets
8 bytes of Michael MIC Authenticator Tx Key – Used to compute MIC on unicast data packets transmitted by the AP
8 bytes of Michael MIC Authenticator Rx Key – Used to compute MIC on unicast data packets transmitted by the station
The Group Temporal Key is divided into three separate keys:
16 bytes of Group Temporal Encryption Key used to encrypt/decrypt Multicast and Broadcast data packets
8 bytes of Michael MIC Authenticator Tx Key used to compute MIC on Multicast and Broadcast packets transmitted by AP
8 bytes of Michael MIC Authenticator Rx Key currently unused as stations do not send multicast traffic
The Michael MIC Authenticator Tx/Rx Keys in both the PTK and GTK are only used if the network is using TKIP to encrypt the data. This four-way handshake has been shown to be vulnerable to KRACK.
Group key handshake
The Group Temporal Key used in the network may need to be updated due to the expiration of a preset timer. When a device leaves the network, the GTK also needs to be updated. This is to prevent the device from receiving any more multicast or broadcast messages from the AP. To handle the updating, 802.11i defines a Group Key Handshake that consists of a two-way handshake:
The AP sends the new GTK to each STA in the network. The GTK is encrypted using the KEK assigned to that STA, and protects the data from tampering, by use of a MIC.
The STA acknowledges the new GTK and replies to the AP.
CCMP overview
CCMP is based on the Counter with CBC-MAC mode of the AES encryption algorithm. CCM combines CTR for confidentiality and CBC-MAC for authentication and integrity. CCM protects the integrity of both the MPDU Data field and selected portions of the IEEE 802.11 MPDU header.
Key hierarchy
RSNA defines two key hierarchies:
Pairwise key hierarchy, to protect unicast traffic
GTK, a hierarchy consisting of a single key to protect multicast and broadcast traffic
The description of the key hierarchies uses the following two functions:
L - From Str starting from the left, extract bits F through F+L–1.
PRF-n - Pseudo-random function producing n bits of output, there are the 128, 192, 256, 384 and 512 versions, each of these output these number of bits.
The pairwise key hierarchy utilizes PRF-384 or PRF-512 to derive session-specific keys from a PMK, generating a PTK, which gets partitioned into a KCK and a KEK plus all the temporal keys used by the MAC to protect unicast communication. The GTK shall be a random number which also gets generated by using PRF-n, usually PRF-128 or PRF-256, in this model, the group key hierarchy takes a GMK and generates a GTK.
"The Protected Frame field is 1 bit in length. The Protected Frame field is set to 1 if the Frame Body field contains information that has been processed by a cryptographic encapsulation algorithm. The Protected Frame field is set to 1 only within data frames of type Data and within management frames of type Management, subtype Authentication. The Protected Frame field is set to 0 in all other frames. When the bit Protected Frame field is set to 1 in a data frame, the Frame Body field is protected utilizing the cryptographic encapsulation algorithm and expanded as defined in Clause 8. Only WEP is allowed as the cryptographic encapsulation algorithm for management frames of subtype Authentication."
