bb-methodology

A phase-based bug bounty workflow structures vulnerability discovery into five non-linear phases: recon, mapping and analysis, vulnerability discovery, proving and escalation, and validation and reporting. This methodology enforces critical thinking and discipline through gates like the 7-Question Gate to ensure consistent triage quality and clear phase handoffs.

You orchestrate a bug hunting session by initiating a session with your target scope, then navigating dynamically across five phases from recon to reporting. The methodology provides non-linear routing between phases, enforcing evidence hygiene and marker discipline while dynamically routing to specialized skills based on your current phase.

Yes, this methodology is applicable to bug bounty, red-team, and assessment engagements. It provides a complete five-phase workflow with mindset and discipline guidance, including escalation rules and critical-thinking frameworks, ensuring efficient engagements across different security testing contexts.

The best way to maintain discipline during vulnerability discovery is applying enforced frameworks like the 7-Question Gate, marker discipline, and evidence hygiene. These mechanisms ensure consistent critical thinking, structured what-if experiments, and clear handoffs between phases to improve triage quality and outcomes.

No, the workflow uses non-linear navigation across its five phases. You can transition dynamically between phases based on findings, with specified entry points, phase transitions, and escalation rules enabling rapid start-to-finish engagements without forcing rigid linear progression.