Documentation and Note-Taking
You'll learn why meticulous documentation is your most critical defense—both during and after a penetration test.
Why Documentation Matters
Imagine trying to prove a security finding to a client three weeks after you discovered it, but you forgot the exact command you ran, the response you got, or which system exhibited the vulnerability. Without documentation, your testing becomes unverifiable theater.
Documentation serves three vital purposes:
- Evidence: Screenshots and logs prove findings existed and were exploitable
- Reproducibility: Clients and defenders must recreate your steps to validate and fix issues
- Legal protection: Detailed records prove you stayed within scope and rules of engagement
Core Documentation Practices
Real-time note-taking is non-negotiable. The moment you run a command, record it. Found something interesting? Screenshot it immediately. Waiting until "later" guarantees you'll forget critical context.
What to document:
- Every command executed with timestamps
- All IP addresses, hostnames, and ports tested
- Screenshots of every finding (before and after exploitation)
- Error messages and unexpected behaviors
- Tools used with version numbers
- Successful and failed attempts
Organization is survival: Use a consistent structure. Many testers organize by target system or by testing phase. Tools like CherryTree, Obsidian, or even markdown files in version control help maintain structure when you're juggling dozens of findings.
Screenshots should tell stories: Capture the full context—terminal commands with output, browser URL bars showing the target, timestamps visible. A cropped image of "Access Denied" means nothing without the URL or command that triggered it.
Key Takeaway: Comprehensive, real-time documentation transforms scattered observations into defensible evidence and actionable intelligence—treat your notes as the deliverable they'll eventually become.