Open Personal Enterprise
Open, WPA2-PSK personal, and WPA2-Enterprise — protocol roles on YOUR lab AP.
Visual · wireless_open_personal_enterprise
Open vs PSK vs Enterprise literacy. $LAB_SSID configs only. Original Cyberlium.
The lock on the door is not the same as the guest list — know which auth mode YOUR lab AP uses.
Open networks have no link-layer auth. Personal (PSK) uses a shared passphrase feeding a 4-way handshake. Enterprise uses 802.1X/EAP per-user credentials — usually with RADIUS. Defenders pick enterprise for workforce WLANs; home labs often use PSK on isolated $LAB_SSID. You compare modes as protocol literacy — not to recommend open cafés or crack stranger PSK. Next: Dot11 Lab.
1. Open vs personal PSK
Open WLANs expose traffic to anyone associated — use only on isolated lab segments. WPA2/WPA3-Personal uses PSK-derived keys; the 4-way handshake proves knowledge of the passphrase without sending it in clear.
Weak PSKs fall to offline guessing — defender lesson is length and uniqueness, not attacking neighbor passphrases.
Command guide
Try these commands — Open vs personal PSK
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Wi-Fi security types — https://www.wi-fi.org/discover-wi-fi/security 802.11 modes — https://www.wi-fi.org/knowledge-center/glossary
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install network-manager
macOS: Use airport / System Settings
Windows: Use netsh wlan (built-in)
═══ LINUX / macOS ═══
Command — copy this
nmcli -f SSID,SECURITY device wifi list 2>/dev/null | grep -E 'WPA|WEP|802.1X|--' | head -15 || nmcli device wifi list | head -10 nmcli device wifi list 2>/dev/null | awk 'NR==1 || /WPA/' | head -10
Primary tools to practice this lesson: nmcli. Reference sites: Wi-Fi security types (https://www.wi-fi.org/discover-wi-fi/security); 802.11 modes (https://www.wi-fi.org/knowledge-center/glossary). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Enterprise 802.1X
Enterprise WLANs authenticate users via EAP methods (PEAP, EAP-TLS, etc.) backed by RADIUS. Compromise shifts to identity infrastructure — certificate validation matters.
Your $LAB_SSID may stay PSK for simplicity; still document which mode you use and why.
3. Defender mapping
Open guest VLANs, PSK home-style, enterprise workforce — each gets different monitoring and hardening. Name your lab mode in RoE.
Ship: auth mode line for $LAB_SSID. Next: Dot11 Lab.
4. What you ship: auth mode statement for $LAB_SSID
Write open vs PSK vs enterprise in one paragraph. State YOUR lab mode. No stranger PSK attacks. chmod 600.
5. What you record before the next lesson
Date. $LAB_SSID auth mode. File t15-m02-l03-open-personal-enterprise.txt chmod 600.
6. Wrong vs right: stranger SSIDs vs YOUR lab AP
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Recommend open Wi-Fi for 'easy capture practice' on café nets. Attack dorm PSK 'because WPA2 is fun.'
- Right: Document YOUR lab auth mode. Next: Dot11 Lab.
Mission: classify YOUR lab WLAN auth
1) State which mode $LAB_SSID uses. 2) One defender hardening note per mode. 3) No neighbor PSK attempts. Never treat open public WLANs as lab.
Stuck? Ask Cyberlium AI Mentor
WPA3-SAE improves PSK — Module 3 goes deeper on protocol generations.
APPLY: WPA2-Personal primarily uses:
APPLY: True or False: Enterprise WLANs typically use 802.1X/EAP with RADIUS.
APPLY: Open WLAN on a public café is: