Skip to main content
Findings arrive from scanners, pentests, bug bounty programs, and advisories faster than anyone can review them. Triage pulls every source into one backlog, tests each finding against your environment, and gives it a verdict. This page gets your first finding triaged. For every source, the verdicts, and automation, see the Triage guide.
The Triage board with findings moving from Untriaged to Investigating and Verdict ready
1

Connect a source

Open Triage and click Add a source. Connect HackerOne, Bugcrowd, GitHub Security Advisories, or a security mailbox directly, or give Neo the API docs for a scanner or any other tool. Neo imports its findings into one backlog. Setup for each source is in Connect a source.
2

Triage a finding

Click Triage on a finding, or drag it into Investigating on the board. Neo starts a task that reads the report, checks for duplicates across your sources, and tests the issue.
3

Review the verdict

When the task finishes, the finding moves to Verdict ready with Neo’s report, evidence, and severity. Accept it and track the fix, or decline it. To push back on a verdict, ask Neo for more proof from the finding’s Activity.
4

Turn on auto-triage

Once a source looks right, turn on auto-triage so new findings get a verdict without anyone starting them.

Triage guide

Every source with a scanner walkthrough, the board and verdicts, and Insights