Evidence Collection and Screenshots
You'll learn how to systematically capture and preserve proof of vulnerabilities in a way that tells a clear, defensible story.
Why Evidence Matters
After exploiting a vulnerability, your findings mean nothing without compelling proof. Think of yourself as a crime scene investigator: you need to document every discovery so thoroughly that someone who wasn't there can understand exactly what happened, reproduce your steps, and verify the risk. Poor evidence collection can turn a critical finding into a disputed "maybe."
Core Principles of Evidence Collection
Screenshots are your primary weapon. Capture every step: before exploitation (showing the vulnerable state), during exploitation (the payload or technique), and after exploitation (the successful result). Always include:
- Timestamps visible in your system clock or terminal
- URLs or command prompts showing where you are
- Unique identifiers like session IDs, usernames, or hostnames
- Full context — don't crop out important details
Logs and network captures provide technical depth. Save:
- HTTP request/response pairs from your proxy tool
- Command output showing exploitation chains
- PCAP files demonstrating network-based attacks
- System logs proving privilege escalation or persistence
Organization is critical. Name files descriptively: 2024-01-15_SQLi_users_table_dump.png beats screenshot1.png. Store evidence per finding, creating a clear trail from discovery to impact.
The Golden Rule
Your evidence should allow independent verification. A reviewer should be able to follow your screenshots like a recipe and reproduce the vulnerability without contacting you for clarification.
Key Takeaway: Evidence collection transforms your technical findings into irrefutable proof—capture every step with clear, timestamped screenshots and supporting logs that tell a complete story anyone can verify.