Timing and Rate Limiting for Evasion
You'll learn how slowing down and spacing out your reconnaissance scans helps you blend into normal network traffic and avoid triggering alarms.
Why Scan Speed Matters
When you perform network reconnaissance, sending thousands of packets per second is fast—but also incredibly obvious. Security systems like firewalls and Intrusion Detection Systems (IDS) watch for sudden bursts of scanning activity. Think of it like a burglar: someone slowly walking past houses over several days looks like a normal pedestrian, but someone frantically checking every door and window in five minutes is clearly suspicious.
The Core Idea
Timing and rate limiting means deliberately slowing down your scans by:
- Adding delays between packets or probe attempts
- Reducing packet rate to match typical network behavior
- Spreading scans over longer periods (hours or days instead of seconds)
By controlling how fast you send reconnaissance traffic, you mimic legitimate network activity—a user browsing slowly, automated monitoring tools running periodic checks, or gradual network exploration rather than aggressive scanning.
How This Helps Evasion
Many detection systems use rate-based thresholds: "If more than X port scan attempts happen within Y seconds, raise an alert." By staying under these thresholds, your scanning activity might never cross the line that triggers investigation.
The tradeoff? Time. What could take seconds now takes hours. But stealth reconnaissance prioritizes avoiding detection over speed.
Practical Perspective
You've already learned about SYN scanning and host discovery. Now imagine running those same techniques but with multi-second delays between each probe. Instead of announcing your presence loudly, you whisper slowly enough that defenders might not notice the pattern.
Key Takeaway: Timing and rate limiting trades speed for stealth, letting your reconnaissance blend into normal network traffic patterns by controlling when and how fast you send packets.