← 返回列表

Introducing Neo Triage

单站 ProjectDiscovery Blog 入库 2026-11-17T04:35:51

Today we're releasing Neo Triage, an autonomous engine for vulnerability triage. While other tools rank your backlog, Neo clears it. It ingests the reports coming in from your scanners, pentesters, and bug bounty researchers, tests each one against your environment, and tells you which ones are real.

It's available today on every Neo plan, including Free, and runs in our cloud, in your own sandboxes, or on-prem.

The bottleneck moved to triage

Finding vulnerabilities got cheap. AI agents probe applications overnight, researchers point models at bug bounty scopes, and scanners ship a check the day a CVE drops. Every one of those reports still ends with a person reproducing it by hand, which takes 15 minutes to four hours per finding. The backlog grows faster than any team can hire, and the few findings that matter sit inside it until someone checks.

Most triage tooling stops at ranking. A scanner scores the finding, a platform prioritizes it, an AI assistant sorts it by how severe it sounds. The list gets better ordered, and it stays the same length, because nothing in it has been tested.

Static triage

Traditional triage is a classifier. It takes what is publicly known about the vulnerability: the CVSS score, the EPSS probability, whether an exploit is published, the version string the scanner matched. It adds what the asset inventory says about the host, usually a tag for internet-facing or holds customer data. A weighted formula turns those into a risk score, and the score sets the order of the queue.

The weakness is in the inputs. None of them come from the running system. The score cannot know that the vulnerable code path is never called, that a WAF rule already blocks the request, that the host sits behind an auth layer the scanner never saw, or that the reporter's proof of concept skips a step.

A sorted backlog is the same backlog. Someone still opens each finding, reproduces it, and decides, and the score did nothing to shorten that.

Dynamic triage

Neo reproduces the finding instead. It opens an isolated sandbox and loads the context for the asset: the application and its APIs, the docs, the network and identity around it, and every prior finding on it. It reads the report, writes down the claim and the exact inputs in the proof of concept, rewrites the reproduction as its own script, and runs it against the real asset.

Each class of bug needs a different instrument to settle it, so the sandbox carries several.

Because the run has the asset's context, it can go further than the report did. A researcher rates an SSRF High. Neo follows the redirect to the metadata service, reads the role credentials it returns, and finds that the role can read customer uploads. The finding comes back Critical, with the chain as evidence. The reverse happens too: a 9.8 that reproduces on nothing you run comes back closed, with the attempts that ruled it out.

Every report ends with a verdict: valid, with the severity Neo measured; likely duplicate, with the original it matches; or informative, not applicable, or spam, with the reasoning. A reviewer accepts, marks duplicate, or declines in one keystroke, and the activity log records who decided what. Insights shows the backlog by week and, at the current rate of closure, when it reaches zero.

What Neo does with every report

Neo handles the full triage loop, from intake to the retest.

A report, start to finish

Every finding opens in a sheet with three tabs.

  1. Original report: the report as it came in, with the program or repository, the reporter, the severity the source gave it, and the CVE and CVSS where there is one.
  2. Triage result: Neo's verdict, the severity it set and who set it, the analysis with the evidence and the request that proved it, and the suggested reply.
  3. Activity: who did what, from the report landing to the retest, each entry with an undo.

Auto triage

Turn on auto triage for a source and new reports are tested without anyone starting them. Neo checks the source on the interval you pick, every 15 minutes to once a day, takes up to 20 new findings at a time in priority order, and runs each one through the same sandbox reproduction as a manual triage. HackerOne can also trigger a run the moment a report lands. The rule runs as the person who saved it, with that person's access.

Each finding reaches the queue with its verdict, severity, and suggested reply already attached, logged as triaged by Auto triage. Your team opens Verdict ready instead of Untriaged.

Security

Neo runs tests against your assets, so every run sits inside these controls.

Availability

Neo Triage is available today on every Neo plan. On the Free and pay-as-you-go plans it is free for a limited time. Enterprise teams get volume pricing based on the size of their backlog.

Getting started

Sign up at neo.projectdiscovery.io, connect your first source, and Neo starts working through your backlog. Setup details are in the docs.

原文链接:https://projectdiscovery.io/blog/introducing-neo-triage