triage-validation

Validate security findings by applying a strict set of criteria to ensure they meet program scope, impact, and authenticity before submission. This process reduces false positives and improves the overall quality of vulnerability reports.

Reduce false positives in vulnerability analysis by running findings through a 7-question gate and 4 pre-submission gates. This strict validation process checks for authenticity and program scope before you report.

The 7-question gate works by applying a comprehensive validation process to assess the viability of a security finding. It ensures the vulnerability meets strict criteria for scope, impact, and authenticity before submission.

Yes, you can use a defined Never Submit List to filter out invalid bug bounty findings. This list identifies specific vulnerability types that should never be submitted, reducing false positives and saving time.

Assess vulnerability severity using the provided CVSS 3.1 Quick Reference guide during security reporting. This reference helps bug bounty hunters accurately score and communicate the impact of validated findings.

Security finding validation limits depend on the strict criteria applied to program scope and impact authenticity. Findings on the Never Submit List are automatically filtered out, and those failing the pre-submission gates are blocked to ensure report precision.