Skip to content
Tutorials Center
My learning

Topics

Lesson 25 of 37 ยท Wireless and Zero Trust

Wi-Fi Security: WPA2, WPA3 and Rogue Access Points

Understand Wi-Fi encryption from WEP to WPA3, how pre-shared keys and 802.1X differ, and how to harden a wireless network and detect rogue or evil-twin access points.

Wireless networks broadcast their traffic into the air. Anyone within range can receive the radio signal, so Wi-Fi security is built on one assumption: the air is hostile. Protection therefore rests on two things: authentication (who may join) and encryption (so that what is overheard is useless). The history of Wi-Fi security is a series of fixes for flaws in these two jobs.

This lesson explains the security generations, the difference between home-style and enterprise authentication, practical hardening, and how defenders spot rogue access points. Nothing here involves breaking into networks; it is the defender's view, for networks you own.

The generations

Standard Year Encryption Status
Open - None Anyone can read everything (see OWE below)
WEP 1999 RC4 with short IV Broken; crackable in minutes. Never use
WPA 2003 TKIP (RC4-based) Deprecated stopgap
WPA2 2004 AES-CCMP Still common; fine with a strong passphrase, but weaknesses exist
WPA3 2018 AES-CCMP/GCMP, SAE handshake Current recommendation

Why WPA2-Personal is exposed to guessing

WPA2-Personal uses a pre-shared key (PSK), the Wi-Fi password. When a device joins, a four-way handshake proves both sides know the key. An attacker who captures that handshake can take it offline and try millions of password guesses per second on their own hardware, with no rate limiting. A long random passphrase makes this hopeless; a short word-based one falls quickly. Also, everyone who knows the PSK can derive the session keys of others if they captured their handshake.

What WPA3 changes

  • SAE (Simultaneous Authentication of Equals) replaces the PSK handshake. Each guess requires live interaction with the access point, so offline dictionary attacks stop working and rate limiting becomes possible.
  • Forward secrecy: capturing traffic now and learning the password later does not decrypt the recording.
  • Protected Management Frames (PMF) are mandatory, which stops forged deauthentication messages that kick clients off.
  • Enhanced Open (OWE) gives open public networks encryption without a password, so passive eavesdropping no longer works (it does not authenticate the access point).
  • A 192-bit mode for high-security enterprise networks.

Transition mode (WPA2 and WPA3 together) helps compatibility but lets attackers downgrade, so use WPA3-only where all clients support it.

Personal versus Enterprise

flowchart LR
    C["Client (supplicant)"] -- "802.1X / EAP" --> AP["Access point (authenticator)"]
    AP -- "RADIUS" --> R["RADIUS server (authentication)"]
    R --> D["Directory / certificates"]

In WPA-Enterprise every user authenticates individually; the AP only relays.

Personal (PSK/SAE) shares one password with everyone. When an employee leaves, you must change the password for all. You cannot tell who did what, and one leaked password exposes the whole network.

Enterprise (802.1X) gives each user or device their own credentials, checked by a RADIUS server using an EAP method:

  • EAP-TLS: client and server certificates. The strongest choice; no passwords to phish.
  • PEAP / EAP-TTLS: a TLS tunnel carries a username and password. Clients must validate the server certificate, otherwise a fake access point can harvest credentials. Misconfigured clients that accept any certificate are a frequent real-world finding.

Enterprise also enables per-user VLAN assignment and instant revocation of one person. See zero trust principles for why identity-based access is the direction of travel.

Hardening checklist

  1. Use WPA3 (SAE) or WPA2-AES at the very least; disable WEP, WPA/TKIP and WPS (the PIN setup feature has design flaws).
  2. Pick a long random passphrase (16+ characters, or a multi-word passphrase) for Personal networks.
  3. Prefer 802.1X with certificates for staff networks.
  4. Enable PMF (802.11w) where clients support it.
  5. Separate guests and IoT onto their own SSID and VLAN, with no route to internal systems (segmentation).
  6. Keep access point firmware updated; change the admin password; disable remote management from the wireless side.
  7. Do not rely on hiding the SSID or MAC filtering; both are trivially bypassed and give a false sense of safety.
  8. Reduce radio coverage to the area you need.

Rogue access points and evil twins

  • A rogue AP is an unauthorized access point connected to your wired network, perhaps a cheap router an employee plugged in. It bypasses your controls.
  • An evil twin is an AP, not connected to your network, that copies the SSID of a legitimate one to lure clients and capture credentials or traffic.

Defenders detect them by inventory comparison: the wireless controller (or a scanning sensor) lists every BSSID heard on your SSIDs, and anything not on the approved list is investigated. The stand-in below checks a made-up scan result against an inventory and flags suspicious signals.

Python Compare scanned access points with the inventory

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The device named CorpWiFi with an unknown MAC address and strong signal is the red flag. Signal strength alone is not proof (a legitimate AP can be loud), which is why teams combine inventory checks, wired-side detection (is an unknown MAC switch-port connected?) and WIPS (wireless intrusion prevention) products that can also contain rogue devices within legal limits.

Public Wi-Fi and the client side

On networks you do not control, assume the network is hostile. Use HTTPS everywhere (how TLS protects you), a trusted VPN if you must, keep automatic joining of open networks off, and forget networks you no longer use, because devices announce remembered names and will auto-join a look-alike.

Wi-Fi password strength is easy to reason about. The program estimates the offline guessing time for a WPA2-PSK-style attacker (illustrative numbers only).

Python How long would offline guessing take?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Eight lowercase letters fall in about a minute at that speed, while 16 random characters take longer than the age of the universe. WPA3's SAE removes the offline option completely, which is why both a good passphrase and a modern protocol matter.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Why is WPA2-Personal vulnerable to offline guessing of weak passphrases?

    The four-way handshake lets an attacker verify guesses offline at hardware speed. WPA3 SAE requires live interaction for each guess.
  2. 2. What does 802.1X with EAP-TLS give that a shared password does not?

    Each client has its own certificate, so access is attributable and revocable without changing a shared password.
  3. 3. Which is an evil twin?

    An evil twin impersonates a real SSID so clients connect to the attacker's device.
  4. 4. Which measure is NOT effective Wi-Fi protection?

    SSIDs and MAC addresses are visible in the air and easy to spoof, so hiding and filtering give a false sense of security.
  5. 5. With PEAP, what must clients do to avoid credential theft by fake access points?

    If clients accept any server certificate, an attacker's fake AP and RADIUS server can collect credentials.

Summary

  • Wi-Fi security relies on authentication plus encryption; WEP and TKIP are obsolete, WPA3 is current.
  • WPA2-PSK handshakes can be attacked offline; WPA3 SAE adds forward secrecy and stops that.
  • Enterprise 802.1X (ideally EAP-TLS) gives individual, revocable access; validate the server certificate.
  • Harden: disable WPS, enable PMF, separate guest and IoT, update firmware; ignore SSID hiding and MAC filtering.
  • Detect rogue APs and evil twins by comparing scans with an inventory and monitoring the wired side.

Next: Zero Trust Principles