report-writing

Write a bug bounty report using impact-first human language and a triager-optimized structure that leads with what an attacker can do. Use platform-specific HackerOne templates with copy-paste reproduction steps and evidence placeholders for consistent evaluation.

Format vulnerability reports using platform-specific templates tailored for Bugcrowd and Intigriti expectations. Apply impact-first summaries, title formulas, and CVSS 3.1 severity decisioning to match each program's required fields and evaluation criteria.

Calculate CVSS 3.1 scores for security triage submissions using built-in quick scoring guidance and severity decision logic. This includes downgrade counters and pre-submit quality checks to prevent vague or qualifying phrasing in the final report.

Yes, the bug bounty report writing approach works for Immunefi submissions by providing platform-specific template sections. It generates submission-ready bodies that align with Immunefi's evaluation fields and impact-first framing requirements.

Bug bounty reports get downgraded when they use qualifying phrasing, lack clear reproduction steps, or miss evidence placeholders. Apply pre-submit quality checks, impact-first summaries, and CVSS 3.1 severity framing to ensure triagers evaluate evidence instead of theory.