Securing Wireless and Mobile Networks
Open in the Padhaiko app4.1 Wireless Security Protocols (WEP, WPA, WPA2, WPA3)
Because wireless LANs (IEEE 802.11 / Wi-Fi) transmit frames over shared open radio spectrum rather than enclosed copper or fiber, any receiver within RF range can eavesdrop or inject frames. Four generations of Wi-Fi security protocols have evolved to address these risks:
| Protocol | Encryption Cipher | Integrity Check | Key Exchange / Auth | Status & Major Weakness |
|---|---|---|---|---|
| WEP | RC4 (- or -bit key + -bit IV) | CRC-32 (ICV, linear) | Static shared key | Broken: -bit IV repeats quickly; FMS/PTW attacks crack key in under a minute |
| WPA | TKIP (RC4 with per-packet key mixing + -bit IV) | Michael (-bit MIC) | PSK (4-way handshake) or 802.1X | Deprecated: Weak RC4 base; vulnerable to Beck–Tews TKIP MIC attacks |
| WPA2 | CCMP (AES-128 CTR + CBC-MAC) | CBC-MAC (-bit MIC) | PSK (4-way handshake) or 802.1X | Widely deployed: Personal PSK vulnerable to offline dictionary attacks; KRACK if unpatched |
| WPA3 | CCMP-128 (Personal) / GCMP-256 (Enterprise 192-bit) | AES-CBC-MAC / GMAC | SAE (Dragonfly) or 802.1X | Current standard: Forward secrecy, blocks offline brute force, mandates PMF |
Key Technical Details
- Why WEP Failed: WEP concatenates a -bit plaintext Initialization Vector () to a static shared key to seed RC4. Because IVs is tiny on busy Wi-Fi links, the birthday paradox guarantees IV reuse after only frames—exposing XORed plaintexts and leaking key bytes via the Fluhrer–Mantin–Shamir (FMS) and PTW attacks. Moreover, CRC-32 is linear, allowing attackers to flip ciphertext bits and fix the checksum without knowing the key.
- WPA (TKIP): Designed as a firmware-upgradeable stopgap for WEP hardware, TKIP doubled the IV to bits, added per-packet key mixing, and replaced CRC-32 with the Michael MIC and a sequence counter. Still built on RC4, it was phased out once AES hardware became standard.
- WPA2 (IEEE 802.11i): Replaced RC4 with AES-CCMP. In WPA2-Personal, client and AP derive a Pairwise Transient Key (PTK) from the Pre-Shared Key (PSK) via a 4-way handshake. Because the handshake contains a cryptographic exchange verifiable offline, an attacker who captures the 4-way handshake (or PMKID) can run high-speed offline dictionary attacks against weak passphrases.
- WPA3: Replaces PSK in Personal mode with SAE (Simultaneous Authentication of Equals), a zero-knowledge password-authenticated key exchange (Dragonfly). Every login performs an interactive negotiation so offline dictionary attacks fail and past sessions enjoy Forward Secrecy. WPA3 also mandates Protected Management Frames (PMF, IEEE 802.11w)—preventing forged deauthentication floods—and adds OWE (Opportunistic Wireless Encryption) for unauthenticated public hotspots.
4.2 Wireless Network Security Mechanisms (Authentication, Encryption and Secure Configuration, Hotspot Security, IEEE 802.1X)
1. Authentication, Encryption, and Secure Configuration
Robust Wi-Fi security combines:
- Strong Authentication: Per-user credentials or client certificates (Enterprise) or strong SAE passphrases (Personal).
- Authenticated Encryption (AEAD): AES-CCMP or AES-GCMP, which simultaneously guarantee confidentiality and frame integrity.
- Secure AP Configuration: Disabling legacy WEP/TKIP fallback, enforcing PMF, disabling WPS, and isolating management interfaces.
2. IEEE 802.1X Port-Based Network Access Control
In enterprise and campus networks (WPA2/WPA3-Enterprise), sharing a single passphrase across hundreds of users is unsafe (if one employee leaves, the whole organization must re-key). IEEE 802.1X solves this using three architectural roles:
IEEE 802.1X Components and Port Model
- Supplicant: The wireless client software/device requesting network access.
- Authenticator: The network access device (Access Point or switch) sitting between client and LAN. It maintains two logical ports: an uncontrolled port (allows only EAPOL authentication traffic) and a controlled port (initially closed; opened for normal IP traffic only after authentication succeeds).
- Authentication Server: A backend RADIUS (or Diameter) server that validates credentials/certificates using EAP (Extensible Authentication Protocol) methods such as EAP-TLS (mutual certificates, strongest), PEAP, or EAP-TTLS.
Each authenticated user receives a unique per-session Pairwise Master Key (PMK), preventing peer users on the same SSID from decrypting each other's traffic.
3. Hotspot Security
Public Wi-Fi hotspots (cafes, airports, hotels) often run open SSIDs or shared passwords, exposing users to local packet sniffing, ARP spoofing, and fake captive portals.
- Infrastructure side: Deploy OWE (WPA3 Enhanced Open) so frames are encrypted without requiring a password, and enable Client/AP Isolation so guests cannot probe each other.
- Client side: Enforce HTTPS-only browsing, disable automatic connection to open networks, and route all traffic through a trusted VPN (IPsec/WireGuard/TLS).
4.3 Threats in Wireless Networks (Rogue Access Points, Sniffing)
- Rogue Access Point: An unauthorized AP physically connected to a trusted corporate Ethernet jack (e.g., an employee plugging in a cheap home router). Because it sits inside the wired perimeter firewall, an attacker outside the building can connect wirelessly and bypass perimeter defenses.
- Countermeasures: IEEE 802.1X on wired switch ports, DHCP snooping, and Wireless Intrusion Prevention Systems (WIPS) performing RF sweeps.
- Evil Twin Access Point: An attacker sets up a malicious AP broadcasting the exact same SSID (and often spoofed BSSID) as a legitimate corporate or cafe network, usually at higher transmit power. Combined with forged deauthentication frames (when PMF is off), victims drop from the real AP and auto-associate to the Evil Twin, enabling Man-in-the-Middle interception, DNS spoofing, and fake captive-portal credential harvesting.
- Wireless Sniffing (Eavesdropping): Putting a wireless adapter into monitor mode captures all 802.11 management, control, and data frames on a channel without associating. On open or WEP networks, payloads are immediately readable; on WPA2-PSK, sniffing captures the 4-way handshake for offline GPU password cracking.
- Jamming and DoS: Broadband RF noise or targeted 802.11 deauthentication/association floods deny service (mitigated partially by PMF / 802.11w against frame-based DoS).
Quantifying WEP IV Collisions and WPS PIN Weakness
(a) Using the birthday-bound approximation for possible WEP Initialization Vectors, estimate how many encrypted frames are transmitted before a probability of IV reuse occurs. (b) Wi-Fi Protected Setup (WPS) uses an -digit PIN, but validates the first digits and the next digits separately (the th digit is a checksum). Compute the maximum number of online guesses needed to brute-force WPS and compare it to a true -digit space.
Estimate the WEP -bit IV collision threshold:
With :
At frames per second, an IV collision happens in roughly seconds!
Compute the WPS split-PIN search space: Because the AP reveals whether the first digits match before checking the next digits (and the th digit is a deterministic Luhn-style checksum):
Compared to combinations, splitting reduces the brute-force effort by a factor of:
allowing recovery within hours unless WPS is disabled.
(a) IV reuse occurs around frames. (b) WPS requires at most guesses ( weaker than ), which is why WPS must be disabled on APs.
4.4 Mobile Device Security (Device Encryption, Authentication, Application Permissions and Security Updates)
Smartphones and tablets travel outside the corporate firewall, connect to untrusted cellular and Wi-Fi networks, and carry sensitive personal and enterprise data. Mobile security rests on four pillars:
- Device Encryption:
- Modern Android (File-Based Encryption, FBE) and iOS (Data Protection) encrypt user storage with hardware-bound keys stored inside a Trusted Execution Environment (TEE) or Secure Enclave.
- Even if an attacker removes the flash chip or boots a custom recovery, data remain unreadable without unlocking the key using the user's passcode/biometric.
- Authentication & Endpoint Control:
- Enforce strong alphanumeric passcodes or + digit PINs (never -digit trivial PINs), backed by hardware rate limiting and auto-wipe after repeated failures.
- Combine local biometrics (fingerprint/face unlock) with Mobile Device Management (MDM/UEM) for corporate BYOD devices—enabling containerization, compliance checks, and remote lock/wipe upon theft.
- Application Permissions & Sandboxing:
- Mobile OSes isolate each app inside its own sandbox (unique UID/SELinux domain) so one app cannot read another app's private data.
- Enforce Least Privilege on runtime permissions (Location, Camera, Microphone, Contacts, Storage): grant "Only while using the app", audit unused permissions, avoid rooted/jailbroken devices (which break sandbox integrity), and install apps only from vetted official stores.
- Security Updates:
- Promptly apply OS, browser/WebView, app, and cellular baseband firmware updates to patch zero-click RCE and privilege-escalation flaws; retire devices past vendor security End-of-Life (EOL).
4.5 Wireless Access Control and Security Measures (MAC Filtering, SSID Security, Guest Networks, Network Segmentation and Secure Access Point Configuration)
| Measure | Security Value | Key Limitation / Best Practice |
|---|---|---|
| MAC Filtering | Low (obscurity/inventory only) | -bit MAC addresses are broadcast in plaintext in 802.11 headers and trivially spoofed; never rely on it as primary auth |
| Hidden SSID (Disable Broadcast) | Negligible | Client devices actively probe for hidden SSIDs in plaintext; can even increase tracking risk. Use a neutral, non-identifying SSID instead |
| Guest Networks | High (with segmentation) | Isolate guests on a dedicated VLAN, enable AP/Client Isolation, block access to internal LAN subnets, and throttle bandwidth |
| Network Segmentation | High | Separate Staff (802.1X), Guests, Corporate IoT/Cameras, and Management onto distinct VLANs with stateful firewall rules between them |
| Secure AP Configuration | High | Change default admin creds, disable WPS, disable remote WAN management, set WPA3/WPA2-AES + PMF, reduce excess TX power |
Tracing an IEEE 802.1X Authentication Exchange (Exam Model)
Explain the step-by-step message flow when a laptop joins a campus Wi-Fi network secured with WPA2/WPA3-Enterprise (IEEE 802.1X / EAP-TLS), identifying the roles of the Supplicant, Authenticator, and RADIUS server.
Association and Controlled Port Blocking: The laptop (Supplicant) associates with the campus Access Point (Authenticator). Initially, the AP keeps its controlled port closed, blocking all DHCP, DNS, and Internet IP traffic while keeping the uncontrolled port open solely for EAPOL (EAP over LAN) frames.
EAP Negotiation and RADIUS Forwarding: The AP sends an EAP-Request/Identity frame to the laptop. The laptop replies with its identity, which the AP encapsulates into a RADIUS Access-Request packet and forwards over the wired network to the Authentication Server (RADIUS).
Mutual TLS Certificate Verification and Key Derivation: Inside EAP-TLS, the RADIUS server and laptop mutually verify X.509 certificates and derive a fresh session secret (MSK / PMK). Upon success, RADIUS sends RADIUS Access-Accept along with the PMK to the AP.
4-Way Handshake and Port Opening: The AP and laptop execute the 802.11 4-way handshake using the unique PMK to install per-session AES encryption keys, and the AP opens the controlled port, assigning the user to their authorized campus VLAN.
The Authenticator (AP) blocks IP traffic on the controlled port until the Supplicant and RADIUS Authentication Server complete mutual EAP-TLS verification and deliver a unique per-session PMK for the 4-way handshake.
Auditing and Hardening a Small Office Wi-Fi Setup (Exam Model)
An office currently secures its single Wi-Fi router using WPA-TKIP, hidden SSID, MAC filtering, WPS enabled, and lets visitors join the same network. Identify four security flaws in this setup and propose concrete fixes.
Identify the four flaws:
- WPA-TKIP: Uses deprecated RC4/TKIP vulnerable to cryptographic attacks.
- False sense of security (Hidden SSID + MAC filtering): MACs and hidden SSID probes travel in plaintext and are trivially spoofed/sniffed.
- WPS enabled: Allows an attacker to brute-force the split -digit PIN in hours.
- Flat shared network for guests: Visitors share the broadcast domain with office servers and workstations.
Specify concrete hardening actions:
- Upgrade encryption to WPA3-Personal (SAE) or WPA2/WPA3-Enterprise (802.1X + AES-CCMP) with PMF (802.11w) enabled.
- Disable WPS completely and change the AP admin password and management interface to wired/VPN-only HTTPS.
- Restore normal neutral SSID broadcast (stop relying on hidden SSID/MAC filtering for security).
- Create a segmented Guest VLAN with Client Isolation and firewall rules blocking all RFC 1918 internal subnets.
Replace WPA-TKIP with WPA3/WPA2-AES + PMF, disable WPS, stop relying on hidden SSID/MAC filtering, and isolate visitors onto a segmented Guest VLAN with client isolation.
Exercises
Compare the -bit IV space of WEP against the -bit Packet Number (PN) space of WPA2-CCMP. How many times larger is the WPA2 PN space, and why does WEP fail so quickly on busy networks?
Compute both spaces and their ratio:
Explain why WEP fails: Because is small, random or sequential -bit IVs repeat after only frames by the birthday bound. Reusing an RC4 keystream XORs two plaintexts together () and enables statistical FMS/PTW key recovery within minutes, whereas packets at would take nearly to exhaust.
The WPA2 -bit PN space is times larger than WEP's -bit IV space; WEP collapses rapidly because frequent IV collisions leak RC4 keystream and enable statistical key recovery.
Compare WEP, WPA, WPA2, and WPA3 in terms of encryption algorithm, integrity mechanism, authentication/key exchange, and resilience against offline dictionary attacks.
Compare all four protocol generations:
- WEP: RC4 + -bit IV, linear CRC-32 integrity, static shared key; completely broken.
- WPA: TKIP (RC4 + -bit IV + key mixing), Michael -bit MIC, PSK/802.1X; deprecated due to RC4/TKIP flaws.
- WPA2: AES-CCMP (-bit AES CTR + CBC-MAC), PSK 4-way handshake or 802.1X. Strong encryption, but WPA2-Personal is vulnerable to offline dictionary attacks on captured 4-way handshakes.
- WPA3: AES-CCMP-128 (or GCMP-256 in Enterprise 192-bit), mandates PMF (802.11w), and replaces PSK with SAE (Dragonfly)—defeating offline dictionary attacks and providing Forward Secrecy.
WEP uses broken RC4/CRC-32, WPA uses deprecated TKIP/Michael, WPA2 introduces AES-CCMP (though PSK allows offline cracking), and WPA3 adds SAE and mandatory PMF to block offline dictionary and deauth attacks.
Describe how an Evil Twin attack works in wireless networks and explain two technical defenses that protect users and enterprise LANs against it.
Explain the Evil Twin attack: An attacker deploys a malicious AP advertising the exact SSID of a legitimate network at high signal strength, often sending spoofed deauthentication frames to force nearby clients off the real AP. Once victims auto-connect to the Evil Twin, the attacker sits in a Man-in-the-Middle position to sniff unencrypted traffic, spoof DNS, or serve a fake captive portal to steal credentials.
Specify two technical defenses:
- WPA3 / Protected Management Frames (IEEE 802.11w) + SAE or 802.1X (EAP-TLS): PMF cryptographically authenticates deauthentication frames so attackers cannot forcibly disconnect clients, and EAP-TLS requires mutual certificate verification so clients reject rogue APs lacking the organization's RADIUS certificate.
- Wireless Intrusion Prevention System (WIPS) + VPN: WIPS sensors monitor RF channels for unauthorized BSSIDs broadcasting corporate SSIDs and alert/contain them, while client-side VPNs encrypt all traffic even if a user accidentally joins a hostile hotspot.
An Evil Twin mimics a trusted SSID (often paired with deauth floods) to intercept client traffic. Defenses include 802.1X (EAP-TLS) + PMF (802.11w) for cryptographic AP/management verification and WIPS monitoring + client VPNs.
Explain why MAC address filtering and disabling SSID broadcast do not provide reliable wireless security, and describe how Guest Networks should be configured instead.
Critique MAC filtering and hidden SSIDs:
- MAC Filtering: Every 802.11 frame header transmits the client's MAC address in plaintext (even on WPA3). An attacker sniffing in monitor mode sees an authorized MAC and clones it in seconds.
- Hidden SSID: Suppressing beacons forces legitimate client devices to actively broadcast probe requests containing the hidden SSID name wherever they travel—leaking the SSID in plaintext and enabling client tracking.
Describe proper Guest Network configuration: Assign guests to a separate VLAN and IP subnet, enable AP/Client Isolation (blocking peer-to-peer Wi-Fi traffic), apply stateful firewall rules denying access to all internal RFC 1918 LANs, enable OWE/WPA3 or portal terms, and enforce DNS filtering and bandwidth limits.
Both MAC addresses and hidden SSIDs leak in plaintext over the air and are trivially spoofed/discovered. Guest access should instead use a dedicated VLAN, Client Isolation, and strict firewall rules blocking internal LAN subnets.
Outline four core security controls for enterprise and personal mobile devices (BYOD), explaining the threat each control mitigates.
Detail the four mobile security controls:
- Hardware-Backed Device Encryption (FBE / Data Protection): Protects stored emails, tokens, and files against physical extraction if the phone is lost or stolen.
- Strong Authentication & MDM Remote Wipe: Blocks unauthorized local access via strong passcodes/rate-limited biometrics and allows IT to lock or wipe lost BYOD containers remotely.
- Application Sandboxing & Least-Privilege Permissions: Isolates apps from each other's data and restricts sensitive sensors (camera, mic, location) so malicious or over-privileged apps cannot spy or exfiltrate corporate data.
- Timely OS, Baseband, and App Security Updates: Patches critical kernel, browser, and cellular radio vulnerabilities before exploit kits target unpatched devices.
Device encryption prevents offline data extraction on theft; strong auth/MDM prevents unauthorized use; app sandboxing & permission hygiene limit malicious app access; timely OS/baseband updates close exploitable CVEs.