WPA3-Enterprise

WPA3-Enterprise is the corporate 802.1X model with the cryptography turned all the way up. Like WPA2-Enterprise, every user authenticates through an EAP exchange that a RADIUS server validates, so there is no shared passphrase to capture or crack. What WPA3-Enterprise adds is the optional 192-bit security mode, also called Suite-B-192, defined in the Wi-Fi Alliance WPA3 specification on top of IEEE 802.11. In that mode the entire suite is matched to a 192-bit security level: data is encrypted with GCMP-256, management frames are protected with BIP-GMAC-256, key derivation uses SHA-384, and the EAP method must be EAP-TLS (RFC 5216) carried over a certificate chain of at least 384-bit ECC (P-384) or RSA-3072.

The headline upgrade over WPA2-Enterprise is that Protected Management Frames (PMF) are mandatory rather than optional. WPA2-Enterprise could be deployed with PMF off, leaving it open to deauthentication and disassociation spoofing; Suite-B-192 forecloses that by requiring ieee80211w=2. The result is mutual certificate authentication, forward secrecy from the TLS handshake, and forged-frame protection, all at a consistent 192-bit strength.

Like WPA2-Enterprise, the protocol-specific fields are EAP Identity and EAP Password, which must correspond to an actual user in the LDAP Directory so test clients and deployed pack members can authenticate against RADIUS / 802.1X for real. The one Suite-B caveat: most client devices need explicit Suite-B support to join at all, so expect a smaller test fleet than WPA2-Enterprise.

Starting the network opens the Enterprise Network Preflight dialog, which checks for a CA, a server certificate, an LDAP directory with users, and a running FreeRADIUS, then either Start Network or Auto-provision & Start (which bootstraps the whole stack, see Certificates, and prints the provisioned test credentials).

For the full New-Network walkthrough and the preflight dialog, see Networks.

Suite-B-192 closes the air-side cracking paths. There is no PSK and no four-way handshake to grind, and mandatory PMF blocks deauthentication. The remaining surface is the same 802.1X plumbing the corporate world relies on: the client's trust decisions and the RADIUS transport behind the AP.

Rogue AP with a forged EAP server

If a client does not pin its CA and server name, a look-alike AP can present any certificate and harvest the inner exchange. Stand up a hostile EAP endpoint and watch what associates:

wpa_supplicant -c eap-tls.conf -i wlan0 -d

Judgment: this is a client-misconfiguration attack, not a protocol break. Against a client that validates the server certificate it fails outright.

RADIUS transport forgery (Blast-RADIUS)

The 802.1X result is relayed in RADIUS, and the RADIUS/UDP Access-Accept Response Authenticator is an MD5 construction. The 2024 attack tracked as CVE-2024-3596 forges that authenticator via an MD5 chosen-prefix collision, turning an Access-Reject into an Access-Accept on the wire (RFC 2865). Reach the RADIUS path and confirm the result an endpoint receives:

eapol_test -c eap-tls.conf -a 10.0.0.1 -s testing123

Judgment: this targets the RADIUS server, not 802.11; it is mitigated by Message-Authenticator enforcement or RADIUS over TLS (RadSec), and it never touches a correctly hardened link.

Mixed-mode downgrade

A migration SSID that also accepts plain WPA2-Enterprise lets a forced fallback skip Suite-B and its mandatory PMF, reopening the older protocol's weaker ciphers and deauthentication surface.

airodump-ng -c 36 --bssid AA:BB:CC:DD:EE:FF wlan0mon

Judgment: the weakness lives in the lower tier, not in Suite-B; a pure WPA3-Enterprise deployment removes it entirely.

Genuine Suite-B-192 deployments are rare and concentrated in government, defense, and regulated environments that must meet the 192-bit bar; the certificate handling and the client-support tax keep most enterprises on WPA2-Enterprise. Where you do meet it, the productive findings are almost never the radio. They are the PKI and the clients: expired or never-published CRLs, an OCSP responder that fails open, a CA that signs anything, and laptops or phones provisioned with server-certificate validation switched off. The cryptography on the air is sound; the operational lifecycle around the certificates is where mistakes accumulate.

Deploy pure Suite-B-192 with no WPA2-Enterprise fallback on the same SSID so there is nothing to downgrade to. Mandatory PMF (ieee80211w=2) is already enforced by the mode and should never be relaxed. The decisive control is the client: push a managed profile that pins the expected CA and RADIUS server name and refuses to connect when either is wrong, because a client that validates the server certificate defeats every rogue-AP variant above.

Behind the AP, harden RADIUS against CVE-2024-3596 by requiring the Message-Authenticator attribute on all packets or, better, running RADIUS inside TLS (RadSec) so the MD5 authenticator is never exposed. Keep the PKI healthy: short certificate lifetimes, published CRLs or a reliable OCSP responder, and a CA that issues only to enrolled devices. Suite-B-192 gives you the strongest link the standard defines, but its security is only ever as good as the certificate validation at both ends.

• IEEE 802.11-2020, Wireless LAN MAC and PHY Specifications (RSN, PMF/BIP, GCMP ciphers)
• Wi-Fi Alliance WPA3 Specification (192-bit security mode, Suite-B-192 requirements)
• RFC 5216 - The EAP-TLS Authentication Protocol
• RFC 2865 - Remote Authentication Dial In User Service (RADIUS)
• CVE-2024-3596 - RADIUS Response Authenticator forgery (Blast-RADIUS)