Skip to main content

Cotool + HackerOne

Connect HackerOne to Cotool so new reports arrive as alerts and agents validate them against your code and logs, comment, change state, and close reports.

Vulnerability & Bug Bounty
Updated

The short answer

Cotool's HackerOne connector turns incoming reports into alerts through webhook-triggered intake for vulnerability response workflows, and agents can comment on, change the state of, and close HackerOne reports.[1]

How it connects: Cotool calls the HackerOne Customer API. HackerOne uses HTTP Basic authentication with an API token's identifier as the username and its value as the password.[2][6]

What Cotool uses from HackerOne

Reports
Agents read reports and can filter them by state, such as needs-more-info, duplicate, or informative, to find what still needs work.[1][7]
Webhook intake
New report events reach Cotool through a webhook trigger and become alerts that start a vulnerability response agent.[1]

Response actions

These change state in HackerOne, so they are the steps teams usually gate behind approval.

Comment, change state, and close
Agents post comments and move reports between states. In HackerOne, closing a report as resolved automatically recognizes the finder in the program's hall of fame and gives reputation.[1][7]

Detections, hunts, and triage

Validate a new reportTriage
When a report arrives, the agent checks the affected asset, reads the relevant code in GitHub, and searches logs for the reported behavior before proposing a state.[1][3][4]
Track the fixResponse
After triage, the agent opens a ticket for the owning team and comments on the report so the researcher sees progress.[1][5]

Setup and permissions

An Admin user generates an API token from the organization's settings page. The token can act only on programs and teams the API user is part of.[6][7]

PermissionAccess
API token (read)Read reports for programs the API user belongs to.[6][7]Read
API token (write)Comment and change report state. Plans with read-only API access reject writes with 403.[6]Write
  • API users cannot be assigned to reports; only users and groups in the program can.[7]

How Cotool works with HackerOne

  • Cotool added the HackerOne connector in release 0.57.0 and report comments, state changes, and closing in release 0.73.0.[1]

FAQ

Does every HackerOne plan allow write access?
No. HackerOne returns 403 for writes when the organization's plan only includes read-only API access.[6]

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Integrations (Cotool) · accessed November 16, 2026
  3. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  4. GitHub integration (Cotool docs) · accessed November 16, 2026
  5. Jira integration (Cotool docs) · accessed November 16, 2026
  6. Getting started (HackerOne API) · accessed November 16, 2026
  7. Customer resources (HackerOne API) · accessed November 16, 2026

Related integrations

All integrations

Use cases with HackerOne

Attackers are scaling with tokens

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

Book a demo