Triage, Communication & Disputes
Bug Bounty Reporting & Career · Bug Bounty track
5 min read
In this module
After You Click Submit
Submitting a report is the start of a process, not the finish line. What happens next — triage, communication, the occasional dispute — determines whether your finding is accepted, how much you're paid, and how your reputation evolves. Handling this phase professionally is every bit as load-bearing as the technical work that preceded it.
The Triage Process
Once submitted, your report enters triage: the process of initial assessment and validation. On most platforms, triage follows a consistent flow:
On HackerOne, triage is done either by the organisation's own security team or by HackerOne's managed triage service, depending on what the programme has bought. On Bugcrowd, managed triage is a core feature: Bugcrowd's internal analysts review reports before forwarding them to the organisation. Managed triage tends to be faster and more consistent, at the cost of having a third party interpret your report before the actual customer ever sees it. Platforms revise these services and their dispute processes regularly, so check the platform's current documentation rather than relying on this summary.
During triage, the analyst will:
- Read your report and verify it is in scope
- Attempt to reproduce the vulnerability using your steps
- Assess the severity against the programme's rating criteria
- Determine if the issue has already been reported (duplicate check)
- Accept, reject, or request additional information
Your report should be clear enough that the triage analyst reproduces the issue without ever contacting you. Each clarification request stalls things by days or weeks.
Handling Duplicates
Duplicates are an unavoidable feature of bug bounty hunting. Multiple researchers test the same targets, and the well-trodden vulnerability classes (XSS, IDOR, SSRF) are crawled by half the platform. When your report is marked a duplicate, it means another researcher beat you to it.
Receiving a duplicate is not a failure. It means your methodology is sound - you found a real vulnerability. The timing simply did not work in your favour. Every active researcher receives duplicates regularly. What matters is how you respond: accept the outcome gracefully, learn from it, and move on to the next target.
When you receive a duplicate:
- Accept it professionally: do not argue unless you have clear evidence that your report describes a genuinely different issue
- Ask for the original report date: some platforms will share when the original report was submitted, which helps you understand the competitive landscape
- Examine what you can learn: if the duplicate is disclosed later, review it to see how the other researcher approached the same issue
- Adjust your strategy: frequent duplicates on a particular programme suggest it is heavily tested - consider moving to a less competitive target
Severity Disagreements
Disagreements about severity are messier than duplicates. You believe a bug is high severity; the triage team rates it as medium. Or the organisation downgrades a finding you consider critical.
Before pushing back, consider whether the disagreement is legitimate:
- Does the organisation have context you lack? They may know about compensating controls, mitigations, or environmental factors that reduce the impact
- Is your CVSS calculation accurate? Review each metric carefully. Common errors include overestimating the scope change, assuming a higher privilege requirement than actual, or misjudging the user interaction requirement
- Does the programme use a custom severity scale? Bugcrowd's P1-P5 taxonomy does not map directly to CVSS. Read the programme's specific rating criteria
If you believe the severity is genuinely incorrect:
- Respond calmly and factually: present additional evidence, a refined CVSS vector, or a more detailed impact analysis
- Demonstrate the attack scenario: sometimes a video showing the full exploitation path changes the assessment
- Reference the programme's own severity guidelines: quote the programme's published criteria and explain why your finding meets a higher tier
- Do not escalate emotionally: accusations, ultimatums, and threats damage your reputation permanently
When to Request Mediation
If direct communication with the programme does not resolve a dispute, platforms offer mediation services. A platform staff member reviews the report, the programme's response, and both parties' arguments, then gives a decision. Whether that decision binds the programme varies by platform and changes over time, so read the platform's current mediation policy.
Request mediation when:
- The programme has stopped responding (no communication for an extended period)
- You believe the severity has been clearly miscategorised and direct discussion has failed
- The programme has changed its scope retroactively to exclude your finding
- Payment has not been made despite the report being accepted and the bug fixed
Do not request mediation for minor disagreements. Reserve it for situations where you have a strong, evidence-based case and direct communication has genuinely failed.
Professional Communication
Every message you send through the platform is part of your professional record. Triage teams, programme managers, and platform staff can see your communication history. Researchers known for professional, constructive communication receive more invitations, better responses, and higher regard from the community.
Principles for communication:
- Be patient - triage teams are often handling hundreds of reports
- Be precise - state facts, provide evidence, avoid speculation
- Be respectful - the person on the other end is doing their job
- Be concise - long messages with embedded frustration are counterproductive
- Be helpful - if asked for clarification, provide it promptly and thoroughly