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.
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
How an AI SOC handles it
Example
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
Integrations used
Sources
- Changelog (Cotool docs) · accessed November 16, 2026
- Jira integration (Cotool docs) · accessed November 16, 2026
- GitHub integration (Cotool docs) · accessed November 16, 2026
- A SIEM built for AI-native security operations (Cotool SIEM) · accessed November 16, 2026
- Linear integration (Cotool docs) · accessed November 16, 2026
- Alerts (Cotool docs) · accessed November 16, 2026
- Customer resources (HackerOne API) · accessed November 16, 2026


