Protected Management Frames (PMF)
You'll learn how 802.11w protects management frames from spoofing and denial-of-service attacks.
The Problem: Unprotected Management Traffic
In traditional Wi-Fi networks (even with WPA2), management frames like deauthentication, disassociation, and beacon frames were always sent unencrypted and unauthenticated. This left a glaring security hole: attackers could forge these frames to disconnect users, perform man-in-the-middle attacks, or create fake access points—even on otherwise secure networks.
Think of it like this: you've secured all the doors and windows of your house (encrypted data frames), but the doorbell and intercom system (management frames) are completely unprotected. Anyone can ring your doorbell pretending to be the police and trick you into opening the door.
How PMF Fixes This
Protected Management Frames (802.11w), now mandatory in WPA3 and optional in WPA2, applies cryptographic protection to critical management frames. It uses the same encryption keys established during the WPA2/WPA3 handshake to:
- Encrypt sensitive management frames (like SA Query)
- Authenticate frames with a Message Integrity Check (MIC)
- Prevent replay attacks using packet number tracking
This means attackers can no longer send fake deauthentication frames to kick users off the network or inject malicious management traffic.
Why It Matters
PMF directly mitigates common Wi-Fi attacks like deauth floods and rogue AP attacks. In WPA3-Personal and WPA3-Enterprise, PMF is always enabled, closing this legacy vulnerability. For WPA2 networks, enabling PMF is a critical hardening step.
Key Takeaway: Protected Management Frames (PMF) use cryptographic authentication and encryption to prevent attackers from forging management frames, stopping deauthentication attacks and other management-layer exploits.