bb-methodology

A non-linear bug bounty hunting methodology orchestrates movement across Recon, Mapping, Discovery, Prove/Escalate, and Validate/Report phases. It applies decision rules for jumping backward when stuck and uses critical-thinking frameworks to choose the next testing experiment.

Structure a bug bounty workflow by applying engagement-mode gating upfront to confirm target validity, then progress through a 5-phase hunting workflow. Use critical-thinking frameworks like developer-psychology reasoning and anomaly detection to guide next testing steps.

Move to the validation and reporting phase after proving maximum business impact during the escalation phase. Run a structured validation gate to ensure finding validity before writing up the deliverable for the specific engagement type.

The best way to decide what to test next when stuck is applying a critical-thinking toolkit using What-If experiments and anomaly detection. The workflow orchestration provides clear rules for jumping backward to earlier phases like Recon or Mapping.

Yes, the methodology forces an explicit engagement-type confirmation at the start of a session. This finding validity discipline ensures you only treat appropriate outcomes as deliverables based on the specific program's engagement rules.

Start using workflow orchestration at the beginning of a hunt session, when switching targets, or whenever you ask what to do next. It requires explicit goal and selection discipline to route between phases, escalation paths, and validation gates.