Skip to main content

Bug bounty report triage

How an AI SOC triages bug bounty reports: check for duplicates, reproduce against code and logs, update the report's state, and ticket the fix.

Use case
Updated

The short answer

Bug bounty report triage decides whether a researcher's report is valid, new, and in scope, and keeps the researcher informed. Cotool takes HackerOne and Bugcrowd reports in through webhook triggers, and agents can comment on, change the state of, and close HackerOne reports.[1]

The problem

Reports move through states such as needs-more-info, duplicate, and informative, and each state change usually comes with a message to the researcher.[7]

States have consequences: closing a HackerOne report as resolved recognizes the finder in the program's hall of fame and gives reputation.[7]

How an AI SOC handles it

  1. Take the report in

    A HackerOne webhook creates an alert and starts the vulnerability response agent.[1]

  2. Check for duplicates

    The agent compares the report with earlier reports and open tickets, using Linear's duplicate issue handling where the team tracks fixes there.[1][2][7]

  3. Reproduce from code and logs

    The agent reads the relevant code in GitHub and searches logs for the reported behavior.[3][4]

  4. Update the report

    The agent comments on the report and moves it to the right state.[1][7]

  5. Ticket the fix

    Valid reports become a Jira or Linear issue for the owning team.[2][5]

Example

Change a HackerOne report's statehttp
POST https://api.hackerone.com/v1/reports/{id}/state_changes
Content-Type: application/json

{
  "data": {
    "type": "state-change",
    "attributes": {
      "message": "Reproduced and assigned to the owning team.",
      "state": "triaged"
    }
  }
}

The HackerOne Customer API call behind a state change, sent with HTTP Basic auth using the API token identifier and value. The message is shown to the researcher.[7]

What people approve

  • Response agents cannot close an alert as True Positive. When an agent confirms malicious activity, it escalates the alert and a person closes it.[6]

How Cotool handles it

  • Cotool added a Bugcrowd integration with webhook triggers for vulnerability intake, and Bugcrowd triggers can create alerts.[1][6]

Integrations used

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Jira integration (Cotool docs) · accessed November 16, 2026
  3. GitHub integration (Cotool docs) · accessed November 16, 2026
  4. A SIEM built for AI-native security operations (Cotool SIEM) · accessed November 16, 2026
  5. Linear integration (Cotool docs) · accessed November 16, 2026
  6. Alerts (Cotool docs) · accessed November 16, 2026
  7. Customer resources (HackerOne API) · accessed November 16, 2026

Related use cases

All use cases

Related reading

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo