Build a recon report — synthesise findings into an attack-surface map
Background
Reconnaissance is the first phase of every engagement. The goal is maximum information with minimum noise — understanding what the target runs, what's exposed, and where the attack surface is before touching any vulnerability.
Real-world examples:
2020 SolarWinds — attackers spent weeks in the reconnaissance phase mapping internal network topology via Orion before deploying SUNBURST. Deep recon enabled surgical targeting.
2021 Accellion FTA — attackers used automated recon to identify Accellion FTA instances (outdated file transfer appliance); .env files exposed via directory traversal revealed DB credentials.
2022 Twilio breach — attacker reconnaissance on GitHub found Twilio employee credentials in public commit history before launching phishing; recon reduced the attack to a single targeted SMS.
Everyday bug bounty — ~60% of valid P1 bugs start with directory/subdomain brute-force finding hidden admin panels, backup files (db.sql.gz), or exposed .git directories.
# Custom wordlist for internal paths
gobuster dir -u "http://victim-adv14:5000" \
-w /usr/share/dirb/wordlists/small.txt \
--add-slash -t 10 --no-error -q 2>/dev/null | head -20
# Manual check of known paths from robots.txt
for path in /_internal/debug /_internal/config /api/v0/admin /api/health/verbose; do
status=$(curl -o /dev/null -s -w "%{http_code}" "$T$path")
echo "$status $T$path"
done