bb-methodology

A non-linear bug bounty workflow coordinates five phases—Recon, Mapping, Find, Prove, and Report—allowing dynamic phase transitions. It streamlines engagements by aligning session goals and routing to specialized toolsets based on the current hunting phase.

Structure a bug hunting session by defining the engagement type and selecting 1–2 vulnerability classes at the start. This activates a five-phase workflow that guides recon, mapping, finding, proving, and reporting for red-team and WAPT-style engagements.

Yes, this methodology applies across bug bounty, red-team, and WAPT-style engagements. It provides a critical-thinking framework and mode-confirmation rules to improve validation and triage quality across different security testing contexts.

Improve validation and triage quality by applying mode-confirmation and discipline rules within a structured workflow. These rules enforce critical thinking during phase transitions, making engagements faster and more reliable.

Yes, the methodology routes to other hunt skills like hunt-dispatch and hunt-auth-bypass to load the right toolset. Cross-skill routing triggers based on the current hunting phase and vulnerability class focus.

A mindset-driven workflow provides consistent, repeatable engagements through structured phase orchestration and critical-thinking frameworks. Ad-hoc hunting lacks mode-confirmation and discipline rules, reducing validation quality and engagement reliability.