domains / families / security / report-writing

report-writing

authentic

Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, severity decision guide, downgrade counters, pre-submit checklist. Use after validating a finding and before submitting. Never use "could potentially" — prove it or don't report.

When to use

• Bug bounty report writing
• Report templates
• Human tone guidelines
• Impact-first writing
• CVSS 3.1 scoring
• Title formula
• Impact statement formula
• Severity decision guide

When not to use

• Using theoretical language like 'could potentially'
• Reporting unproven findings

Skill page

Source