Take notes before you scan
Mapping the attack surface is the most skipped step. A three-column table written as you go beats any tool.
A good penetration test starts by mapping the attack surface. Skip that step and everything after it is guesswork.
Start with what is already public
Before scanning anything, list what the system advertises: DNS, certificates, headers, robots.txt, security.txt.
curl -sSI https://example.com | grep -iE "server|content-security|x-frame"The headers that come back describe the system more honestly than any banner you could guess at.
Notes beat tools
Tools churn every year. Notes do not: a clear timeline of what you tried, what came back, and what you suspect next is the only thing that makes a report hold up.
| Step | Evidence | Hypothesis |
|---|---|---|
| 1 | X-Powered-By header |
Framework leaks its version |
| 2 | 500 error page | An untested code path is reachable |
A table that small, written as you go, is worth more than a long report written at the last minute.
Comments
Get new posts by email
No ads, no tracking. Just new posts, unsubscribe any time.