Fits around the tools you already run
This product does not try to replace your scanner, your ticketing system, or your CMDB. It reads from them, decides what matters, and routes work back out.
Available now
- Nessus, Tenable.sc, Tenable.io. Native .nessus export, read as a stream so a multi-gigabyte file does not need a multi-gigabyte container.
- CSV and TSV. Column names matched against aliases, so an export from almost anything works without a mapping step.
- Built-in discovery. TCP host and service discovery for instances running inside your own network.
- REST API. Push inventory from a CMDB, pull the current risk position into a SIEM or status board.
Planned
- Qualys, Rapid7 InsightVM, and Microsoft Defender live API pulls
- AWS, Azure, and GCP inventory synchronisation
- Jira and ServiceNow task routing
- Slack and Teams alerting on SLA breach
- Automatic CISA KEV and EPSS enrichment on a daily cycle
Listed as planned rather than implied as present. If one of these is the reason you would buy, tell us and we will tell you honestly where it sits.
Why every source goes through the same pipeline
A file import, a live API pull, and the built-in scanner all produce the same intermediate shape and then run through one ingest path. That is what guarantees a host discovered by one source is recognised as the same host by another, rather than three integrations quietly developing three different definitions of "the same machine".
Findings are identified by a stable fingerprint built from the scanner's own check identifier where one exists, so a vendor rewording a check title between releases does not reset the finding's age and restart its SLA clock.
The REST API
Authenticated by API key, scoped per key, available on Professional and above.
GET /api/v1/assets List and filter the inventory
GET /api/v1/assets/{id} One asset with its open findings
GET /api/v1/findings The prioritised queue
GET /api/v1/risks The risk register
GET /api/v1/tasks Remediation work
GET /api/v1/posture A compact summary for a status board