Before we touch a single tool, we need a shared map of the engagement, and the boundaries we never cross.
Pentest phases, red/blue/purple context, and rules of engagement.
Passive vs active recon, and a practical OSINT toolkit.
802.11 basics, scanning, the 4-way handshake, wordlists.
Nmap fundamentals and web content discovery with dirsearch.
Wi-Fi scan · OSINT challenge · Nmap + dirsearch.
What to practice next.
Simulates real attackers to test detection and defenses: recon, exploitation, evasion. Today's focus.
Defends, monitors, and responds: logs, SIEM alerts, incident response.
Red and blue collaborating deliberately, so findings turn into detections.
Pentesting vs. red teaming: a pentest is scoped and breadth-first ("find as many holes as possible"); a red team engagement is objective-driven and stealthy ("reach this goal without being caught"). Today's techniques apply to both.
Passive & active info gathering. No exploitation yet.
Map live hosts, open ports, running services, versions.
Turn a weakness into initial access.
Privilege escalation, lateral movement, persistence.
Findings, evidence, and remediation guidance.
Deep on phases 1-2, plus a guided taste of WPA2 exploitation.
Today's labs run only against your own equipment or an authorized lab environment. Scanning or attacking networks you don't own or lack explicit permission to test is illegal in effectively every jurisdiction, see the GRC & cyber-law guide for the details that apply here.
Everything an attacker learns before they ever send a packet at your infrastructure.
OSINT is intelligence built entirely from publicly available sources, no exploitation, no credentials, just careful looking.
Domains, subdomains, IP ranges, cloud assets.
Employee names, roles, email conventions, usernames.
Tech stack, physical locations, third-party vendors.
Everything you gather here feeds later phases: pretexts, password guesses, and the list of live targets you'll scan.
Domain registrant, nameservers, registration dates.
DNS records: A, MX, TXT, NS: and zone insight.
Certificate Transparency logs reveal subdomains fast.
Automated email & subdomain harvesting from search engines.
Internet-wide search for exposed devices and services.
site: filetype: intitle: inurl: operators.
exiftool on public PDFs/images can leak usernames, software versions, even GPS coordinates.Why proximity alone is enough for wireless to become the softest part of a network.
No cable, no badge, no VPN, just range. That's what makes wireless worth its own module.
Weak or reused PSKs, WPS left enabled, rogue/unmanaged APs, guest networks that bleed into internal VLANs.
Wireless sits in both recon (mapping the physical/wireless footprint) and, with authorization, hands-on testing.
SSID is the human-readable network name; BSSID is the AP radio's MAC address: what you actually target.
2.4GHz and 5GHz, split into channels. Channel + BSSID together pin down exactly one AP to watch.
Normal adapter behavior: connects to one network, ignores everyone else's traffic.
Adapter captures every frame in range, on a channel, without associating. Required for Wi-Fi pentesting.
$ airmon-ng start wlan0 # enable monitor mode → wlan0mon $ airodump-ng wlan0mon # list every AP + client in range $ airodump-ng -c 6 --bssid AA:BB:CC:DD:EE:FF -w capture wlan0mon
The real lesson: WPA2-Personal's security is only as strong as the passphrase. That's the whole reason we're about to talk about wordlists.
14M leaked, real-world passwords. Ships with Kali: the default training dataset.
Curated lists for passwords, usernames, and web content: reused constantly across today's labs.
crunch generates by pattern; cewl scrapes a site for target-specific candidate words.
$ aircrack-ng -w rockyou.txt -b AA:BB:CC:DD:EE:FF capture-01.cap # GPU alternative: $ hashcat -m 22000 capture.hc22000 rockyou.txt
Turning a list of live hosts into a list of actual opportunities.
What's out there? Maps the attack surface: domains, IPs, wireless footprint.
What's actually running on it? Digs into live targets: ports, services, versions, exposed paths.
Enumeration is where a list of IPs turns into a list of opportunities.
$ nmap -sn TARGET_RANGE # host discovery / ping sweep $ nmap -sS -p- TARGET_IP # full TCP SYN port scan $ nmap -sV -sC TARGET_IP # service/version + default scripts $ nmap -sU --top-ports 20 TARGET_IP
SYN scans need raw-socket privileges, that's why nmap usually runs with sudo.
--script=vuln, --script=http-title, and categories like auth, discovery, and safe.-oA scan_results writes normal, XML, and grepable output together.-sn or top ports), then narrow -p- to hosts you know are live.$ dirsearch -u http://TARGET_IP -e php,html,txt,js \ -w /usr/share/wordlists/dirb/common.txt
Found: inspect it.
Redirect or forbidden: it still exists.
Server error: sometimes leaks a stack trace.
Three guided labs, run only against your own gear or an authorized lab range.
Map the wireless environment around the lab AP, then capture one handshake, from the designated target only.
airodump-ng and log every visible AP.A table of ≥5 nearby APs (BSSID, channel, encryption, signal) plus one captured handshake from the designated lab AP.
Build a recon dossier on the provided target persona using passive OSINT only, flags are hidden in what you find.
A 1-page recon dossier, domains/subdomains, key personnel, tech stack, notable exposed files, plus any flags you uncovered.
Enumerate a lab target end-to-end: from open ports to a hidden web path.
-sV -sC on open ports; note every service and version.An enumeration writeup, ports/services table, discovered web paths, and one flag or artifact found via a hidden path.
TryHackMe, HackTheBox, and our own MCTF: all built for exactly this.
SecLists repo, aircrack-ng docs, Nmap reference guide.
Run OSINT + nmap against your own lab machines weekly. Muscle memory matters.