Wireless Security
⚠️ Lab-only rule: Perform the techniques below only on your own Wi-Fi/router, a dedicated test AP, or an authorized CTF/lab. Never test a neighbor's, college, café, or public Wi-Fi without explicit permission.
1. What is Wireless Security?
Wireless security is the process of understanding, assessing, and securing Wi-Fi networks and wireless devices.
As an ethical hacker, your goal is to answer:
- What wireless networks exist?
- Which access points belong to the authorized organization?
- What security protocol is being used?
- Which clients are connected?
- Is the configuration weak?
- Can authentication be attacked?
- Are there rogue/fake access points?
- Can wireless traffic be intercepted?
- How can the network be secured?
A typical wireless attack surface:
Wi-Fi Network │ ┌──────────┴──────────┐ │ │ Access Point Wireless Clients │ ┌────┴────┐ │ Laptop Phone │ ┌────┴─────┐ │ │ Router Internet
2. Wi-Fi Fundamentals
Before attacking Wi-Fi, understand the architecture.
Access Point — AP
The AP provides wireless connectivity.
Example:
SSID: Gyandev_WiFi BSSID: AA:BB:CC:11:22:33 Channel: 6 Security: WPA2-Personal
Client
A device connected to the AP.
Examples:
- Laptop
- Smartphone
- ESP32
- Smart TV
- IoT device
- Printer
SSID
Service Set Identifier
Basically, the Wi-Fi network name users see.
Home_WiFi Office_WiFi Gyandev_WiFi
BSSID
Usually the MAC address identifying a particular wireless interface/AP.
Example:
AA:BB:CC:11:22:33
Important:
SSID = network name
BSSID = wireless interface/AP identifier
3. Wi-Fi Bands
Common Wi-Fi bands:
| Band | Characteristics |
|---|---|
| 2.4 GHz | Longer range, more interference |
| 5 GHz | Higher throughput, shorter range |
| 6 GHz | Newer, cleaner spectrum, Wi-Fi 6E/7 environments |
2.4 GHz is particularly important for security labs because many devices support it.
4. Wi-Fi Channels
Wireless networks communicate using channels.
For example:
2.4 GHz Channel 1 Channel 6 Channel 11
These three are commonly used because they minimize overlap in typical 20-MHz 2.4-GHz configurations.
In real environments you may see:
AP1 → Channel 1 AP2 → Channel 6 AP3 → Channel 11
An ethical hacker should understand channel usage because wireless capture depends on where the AP is operating.
5. 802.11 Frames
Wi-Fi communication uses IEEE 802.11 frames.
Three important categories:
Management frames
Used to manage wireless connections.
Examples:
- Beacon
- Probe Request
- Probe Response
- Authentication
- Association
Control frames
Help coordinate communication.
Examples:
- ACK
- RTS
- CTS
Data frames
Carry actual network data.
Understanding these frames becomes extremely useful when using:
Wireshark
6. Authentication vs Association
These are different stages.
Simplified flow:
Client │ │ Discover AP ▼ AP │ │ Authentication ▼ Client │ │ Association ▼ AP │ │ Security handshake ▼ Encrypted communication
Don't confuse:
Authentication
with
Authorization
or
Association
They are different concepts.
7. Wi-Fi Security Protocols
You should know the evolution:
WEP ↓ WPA ↓ WPA2 ↓ WPA3
WEP
Old and fundamentally insecure.
It should not be used.
WEP attacks are mainly useful for understanding wireless-security history.
8. WPA / WPA2 / WPA3
WPA
Introduced as an improvement over WEP.
WPA2
For many years the standard choice.
Two common modes:
WPA2-Personal WPA2-Enterprise
WPA3
Newer security architecture.
Commonly:
WPA3-Personal → SAE WPA3-Enterprise → 802.1X/EAP
9. WPA2-Personal
You probably use this at home.
Example:
SSID: MyHome Security: WPA2-Personal Password: ********
The password is commonly called the PSK in this context.
A simplified conceptual model:
Wi-Fi Password │ ▼ PSK │ ▼ Authentication / Key Establishment │ ▼ Encrypted Wi-Fi Traffic
A weak password is therefore a major security problem.
10. WPA2-Enterprise
Enterprise Wi-Fi is different.
Instead of everyone sharing one Wi-Fi password, organizations commonly use:
Client │ ▼ Access Point │ ▼ 802.1X │ ▼ RADIUS Server │ ▼ Authentication
This is common in:
- Universities
- Companies
- Hospitals
- Large organizations
You may encounter EAP methods such as:
- EAP-TLS
- PEAP
- EAP-TTLS
11. WPA3 and SAE
WPA3-Personal uses SAE — Simultaneous Authentication of Equals.
Conceptually:
Client AP │ │ │──── SAE exchange ──│ │ │ │──── authentication│ │ │ │══ encrypted data ══│
SAE provides stronger protection against some offline password-guessing scenarios compared with traditional WPA2-PSK authentication.
For an ethical hacker, the important lesson is:
Don't assume every Wi-Fi network can be attacked using the same WPA2 techniques.
12. Wireless Adapter Requirements
Your normal laptop Wi-Fi adapter may not support everything required for wireless security testing.
For many Kali wireless labs, you'll want an external USB adapter that supports:
- Monitor mode
- Appropriate 802.11 bands
- Packet capture
Some advanced testing also requires:
- Frame injection support
13. Managed Mode vs Monitor Mode
This is extremely important.
Managed mode
Normal Wi-Fi operation.
Laptop │ └── Wi-Fi Adapter │ └── Connected to AP
Monitor mode
The adapter listens to wireless frames without behaving like a normal connected client.
Wireless Environment │ ├── AP1 ├── AP2 ├── Client1 ├── Client2 └── IoT │ ▼ Monitor Adapter │ ▼ Packet Capture
14. Check Your Wireless Interface
On Kali:
iw dev
or:
ip link
You may see something like:
wlan0
Check wireless information:
iwconfig
15. Aircrack-ng Suite
One of the most famous wireless security toolsets is:
Aircrack-ng
It contains several utilities.
| Tool | Purpose |
|---|---|
airmon-ng | Monitor-mode management |
airodump-ng | Wireless packet capture/discovery |
aireplay-ng | Frame injection/testing |
aircrack-ng | Key/password analysis |
airdecap-ng | Decrypt captured traffic when appropriate |
airbase-ng | AP simulation/testing |
Think of the suite as:
Discover ↓ Capture ↓ Analyze ↓ Validate ↓ Report
16. Monitor Mode
For your own lab adapter, a typical workflow is:
sudo airmon-ng check
Then:
sudo airmon-ng start wlan0
Depending on your Kali/driver version, you may get an interface such as:
wlan0mon
Check:
iwconfig
You may see:
Mode:Monitor
17. Wireless Discovery with Airodump-ng
In your authorized lab:
sudo airodump-ng wlan0mon
You may see information similar to:
BSSID PWR CH ENC ESSID AA:BB:CC:11:22:33 -40 6 WPA2 Lab_WiFi DD:EE:FF:44:55:66 -65 11 WPA3 Test_AP
Important fields:
BSSID
AP MAC address.
PWR
Approximate received signal strength.
CH
Channel.
ENC
Encryption/security type.
ESSID
Network name.
18. Why Wireless Enumeration Matters
Suppose your lab produces:
SSID: LAB-WIFI BSSID: AA:BB:CC:11:22:33 Channel: 6 Security: WPA2
Now you know:
Target AP │ ├── SSID ├── BSSID ├── Channel ├── Security └── Connected clients
This is the wireless equivalent of building an attack surface.
19. Targeted Capture
Instead of monitoring everything, you can focus your lab capture on a specific AP/channel.
Conceptually:
All Wi-Fi │ ▼ Specific Channel │ ▼ Specific BSSID │ ▼ Capture
For example, in your own lab:
sudo airodump-ng -c 6 --bssid AA:BB:CC:11:22:33 -w lab wlan0mon
This produces capture files that can later be analyzed.
20. Wireshark
Wireshark is extremely important for wireless security.
Open a capture:
wireshark lab-01.cap
You can inspect:
- Beacon frames
- Probe requests
- Probe responses
- Authentication
- Association
- EAPOL
- Data frames
- Management frames
21. What is EAPOL?
With WPA/WPA2, you may encounter:
EAPOL — Extensible Authentication Protocol over LAN
During the WPA2 authentication process, EAPOL frames are involved in the 4-way handshake.
Conceptually:
Client AP │ │ │──── Message 1 ──────►│ │◄──── Message 2 ──────│ │──── Message 3 ──────►│ │◄──── Message 4 ──────│ │ │ └── Encrypted session ─┘
This handshake is extremely important in wireless security testing.
22. WPA2 4-Way Handshake
The purpose is to establish session keys securely.
Very simplified:
AP + Client │ ├── prove knowledge of shared secret │ ├── derive session keys │ ├── confirm keys │ ▼ Encrypted communication
The handshake itself doesn't simply contain the Wi-Fi password in plaintext.
This is a very important misconception to avoid.
23. Password Cracking Concept
If you capture an appropriate WPA2 handshake in your own lab, password security can be tested offline.
Conceptually:
Captured Handshake │ ▼ Candidate Password │ ▼ Cryptographic Verification │ ├── Match → Password correct │ └── No match → Try another
This is why:
Strong Wi-Fi passwords matter.
A short/simple password can potentially be guessed much more easily than a long random one.
For a lab, you can deliberately configure:
SSID: SecurityLab Password: Lab12345
and study the process safely.
24. Deauthentication
You will often hear about:
Deauthentication attacks
Concept:
Client ───── Wi-Fi ───── AP ▲ │ │ │ └── deauth frame ───────┘
A malicious actor attempts to cause a client to disconnect.
Potential reasons an attacker might attempt this include:
- testing wireless resilience
- forcing reconnection in a lab
- studying management-frame security
- demonstrating why protected management frames matter
Important
Do not perform deauthentication against networks or devices you don't own or have explicit permission to test.
In your own lab, this can be studied as part of a controlled wireless-security exercise.
25. PMF / 802.11w
Modern Wi-Fi can use:
Protected Management Frames (PMF)
This helps protect certain management traffic from spoofing.
WPA3 environments generally make stronger use of protected management frames.
This gives you an important defensive question:
Is PMF enabled, optional, or required?
26. WPS Security
WPS — Wi-Fi Protected Setup
Designed to make Wi-Fi setup easier.
Common mechanisms include:
- PIN
- Push Button
- NFC
Historically, some WPS PIN implementations were vulnerable to brute-force attacks.
Therefore, during a security assessment:
Check: │ ├── Is WPS enabled? ├── Which WPS method? ├── Does the AP implement lockout? └── Is WPS actually necessary?
Best defense:
Disable WPS if it isn't required.
27. Evil Twin / Rogue AP
One of the most important wireless concepts.
Suppose the legitimate network is:
Company-WiFi
An attacker creates another AP with a similar or identical name:
Company-WiFi
Conceptually:
Internet │ ┌──────┴──────┐ │ │ Legit AP Rogue AP │ │ Company Fake Wi-Fi Wi-Fi
This is commonly called an:
Evil Twin
28. Why Evil Twins Are Dangerous
A user may connect to the wrong AP.
Potential risks include:
- Credential phishing
- Traffic interception attempts
- Fake captive portals
- Malicious redirects
- Social engineering
Important distinction:
Creating a fake AP isn't automatically proof that encrypted traffic can be decrypted.
Modern HTTPS/TLS provides additional protection.
29. Captive Portal Attacks
You may see captive portals in:
- Hotels
- Airports
- Cafés
- Universities
Example:
Connect Wi-Fi ↓ Captive Portal ↓ Login / Accept Terms ↓ Internet
An attacker could create a fraudulent portal designed to collect credentials.
Defensive testing asks:
- Is the portal authentic?
- Is HTTPS used?
- Are credentials protected?
- Can users distinguish the legitimate portal?
- Are phishing-resistant authentication methods available?
30. MAC Address Spoofing
A wireless interface has a MAC address.
It may look like:
A4:5E:60:12:34:56
Some systems allow changing the locally used MAC address.
Concept:
Original MAC ↓ Modified MAC
But remember:
MAC spoofing does not magically bypass WPA2/WPA3 authentication.
A MAC address is not a password.
31. Wireless Attack Categories
You should know these categories:
| Attack | Concept |
|---|---|
| WEP attacks | Exploit obsolete WEP design |
| WPA/WPA2 password guessing | Offline candidate testing |
| Deauthentication | Disrupt client/AP connection |
| Evil Twin | Fake AP impersonation |
| Rogue AP | Unauthorized AP |
| Captive Portal Phishing | Fake authentication page |
| WPS attacks | Abuse weak WPS implementations |
| MITM | Attempt traffic interception |
| Credential theft | Capture authentication information |
| DoS | Wireless availability disruption |
32. Wireless Enumeration Methodology
As a professional pentester:
1. Define scope ↓ 2. Identify wireless environment ↓ 3. Discover SSIDs/BSSIDs ↓ 4. Identify channels/bands ↓ 5. Identify security protocol ↓ 6. Identify clients ↓ 7. Capture authorized traffic ↓ 8. Analyze configuration ↓ 9. Test authentication controls ↓ 10. Test WPS/management security ↓ 11. Test rogue AP exposure ↓ 12. Document findings ↓ 13. Recommend remediation ↓ 14. Retest
33. Practical Wireless Lab 🔬
For your learning, create this:
YOUR TEST LAB ┌─────────────────┐ │ Test Router │ │ SSID: LAB │ │ WPA2/WPA3 │ └────────┬────────┘ │ ┌──────┴──────┐ │ │ Test Phone Test Laptop ▲ │ Kali Linux │ USB Wi-Fi Adapter Monitor Mode
Use only your own test router/AP and devices.
34. Lab Exercise 1 — Discover Your AP
Start with:
iw dev
Find your wireless adapter.
Then:
sudo airmon-ng start wlan0
Check:
iwconfig
Then:
sudo airodump-ng wlan0mon
Identify your test AP:
BSSID CH ENC ESSID
35. Lab Exercise 2 — Capture Your Own Network
Focus on your own AP:
sudo airodump-ng \ -c <CHANNEL> \ --bssid <YOUR-BSSID> \ -w lab \ wlan0mon
Then open the resulting capture in Wireshark:
wireshark lab-01.cap
Study:
Beacon Probe Authentication Association EAPOL Data
Don't just run commands—understand what every frame means.
36. Lab Exercise 3 — Analyze Your Password Security
Configure your own test AP with a deliberately weak lab password.
For example:
SSID: Uday-Lab Password: Lab12345
Study the authentication process and understand how offline password guessing works.
Then change it to something much stronger, such as a long random password, and compare the security implications.
37. Lab Exercise 4 — Detect Rogue APs
Create:
Legitimate: Uday-Lab Test Rogue: Uday-Lab
Then investigate:
SSID BSSID Channel Signal Security Vendor
Your goal is not to attack users.
Your goal is to learn:
How can a defender distinguish the legitimate AP from a rogue AP?
38. Wireless Security Checklist
During a professional assessment:
Configuration
- WPA2/WPA3 enabled
- WEP disabled
- Strong password
- WPS disabled where unnecessary
- Firmware updated
- Default credentials changed
Authentication
- Strong PSK
- Enterprise authentication configured correctly
- Certificate validation verified
- No unnecessary legacy authentication
Wireless infrastructure
- Rogue AP monitoring
- Unknown AP detection
- Secure management
- Network segmentation
- Guest isolation
Management frames
- PMF evaluated
- Deauthentication resilience tested
- AP configuration reviewed
Monitoring
- Logs enabled
- Alerts configured
- Wireless IDS/IPS where appropriate
39. Most Important Tools
Your wireless toolkit should eventually include:
Aircrack-ng │ ├── airmon-ng ├── airodump-ng ├── aireplay-ng └── aircrack-ng Wireshark Kismet iw ip nmcli
Don't try to memorize every option.
Learn what problem each tool solves.
40. Wireless Attack Thinking 🧠
When you encounter a Wi-Fi network, ask:
What AP exists? ↓ What SSID? ↓ What BSSID? ↓ What channel? ↓ What security? ↓ Which clients? ↓ Is WPS enabled? ↓ Is PMF enabled? ↓ Is authentication strong? ↓ Are rogue APs possible? ↓ Can I safely demonstrate the weakness? ↓ What is the impact? ↓ How do I fix it?
41. The Professional Mindset
Don't become:
“I know Aircrack-ng.”
Become:
“I understand how 802.11 works, how authentication happens, how wireless traffic is protected, how weaknesses can be validated safely, and how to secure the wireless environment.”