vuln-report

Overview

Based on Penetration Testing (Georgia Weidman) and industry bug bounty standards (HackerOne, Bugcrowd). A vulnerability report is the primary deliverable of security testing. Its job is to make the reader understand the risk, believe it is real (evidence), and know exactly how to fix it. Reports that lack clear reproduction steps are ignored. Reports that lack business impact framing are deprioritized.

Weidman's rule: a finding no one acts on is a finding that didn't matter. Write for the engineer who needs to fix it AND the manager who needs to prioritize it.

Workflow

Step 1: Write the finding header

Finding title: [Concise, specific title that names the vulnerability and affected component]
  Good: "SQL Injection in /api/search allows unauthenticated data exfiltration"
  Bad: "SQL Injection Found"