Back

Lesson 8: Timing and Performance

Optimize scan speed and efficiency with timing controls

1 / 4

Understanding NMAP Timing and Performance

NMAP's performance can be fine-tuned through various timing controls and optimization techniques. Understanding these options helps balance scan speed, accuracy, and stealth.

Why Timing Matters

Performance Factors:
  • • Network Latency: Round-trip time affects scan speed
  • • Bandwidth Limitations: Network capacity constraints
  • • Target Response: How quickly targets respond
  • • Firewall Filtering: Dropped packets slow scans
  • • Scan Scope: Number of targets and ports
Trade-offs:
  • • Speed vs Accuracy: Faster scans may miss results
  • • Speed vs Stealth: Aggressive scans are more detectable
  • • Resource Usage: Fast scans consume more CPU/memory
  • • Network Impact: High-speed scans generate more traffic
  • • False Negatives: Impatience can miss slow responses
Default vs Optimized Timing
Default Scan (Slow):
nmap 192.168.1.0/24
Conservative timing, high accuracy
Scan time: ~20-30 minutes for /24
Optimized Scan (Fast):
nmap -T4 --min-rate 1000 192.168.1.0/24
Aggressive timing, good accuracy
Scan time: ~2-5 minutes for /24

Basic Performance Concepts

Parallelization
  • • Multiple hosts simultaneously
  • • Multiple ports per host
  • • Concurrent probe packets
  • • Balances speed and resources
Rate Control
  • • Packets per second limits
  • • Minimum/maximum rates
  • • Adaptive rate adjustment
  • • Bandwidth management
Timeout Control
  • • Host discovery timeouts
  • • Port scan timeouts
  • • Script execution limits
  • • Overall scan timeouts