TCP Stealth Scan Techniques
What you'll learn: How to probe open ports using TCP flags in creative ways that slip past firewalls and avoid leaving obvious traces.
When you performed a SYN scan earlier, you learned how to knock on doors without fully opening them. Now you'll master even sneakier techniques that exploit how firewalls and intrusion detection systems filter network traffic.
Why Stealth Matters
Traditional scans generate logs and trigger alerts. Stealth scans manipulate TCP flags in unexpected ways to probe ports while leaving minimal footprints. Think of it like testing doors in a building: instead of knocking loudly (full TCP connection), you're checking if the lock jiggles differently depending on whether anyone's home.
Core Stealth Techniques
SYN Scan (Revisited): Sends SYN, receives SYN-ACK (open) or RST (closed), then you send RST to abort. Never completes the handshake, so many systems don't log it as a connection attempt.
NULL Scan: Sends a packet with no flags set. According to TCP standards, a closed port should respond with RST; an open port should ignore it (no response). Useful against simple firewalls that only block standard connection attempts.
FIN Scan: Sends only the FIN flag (normally used to close connections). Like NULL scans, closed ports send RST, open ports stay silent. It's like waving goodbye when you never said hello.
Xmas Scan: Sets FIN, PSH, and URG flags simultaneously—lighting up the packet "like a Christmas tree." Same response pattern: RST from closed ports, silence from open ones.
The Catch
These techniques work because many stateful firewalls only inspect SYN packets. However, modern intrusion detection systems recognize these patterns. Windows systems often respond differently than expected, violating the RFC standards these scans rely on.
Key Takeaway: Stealth scans like NULL, FIN, and Xmas manipulate TCP flags to probe ports while evading simple packet filters, but their effectiveness varies by target OS and security infrastructure.