The Problem
Every dashboard, report, and priority list is only as good as the scans underneath it — and most teams have no idea what their scans are missing. Uncredentialed hosts quietly report a fraction of their real findings, slow scans age the data, and nobody notices until a "clean" asset turns out to have been half-blind all along.
What It Does
Chronos tells you what your scans can't see before you trust the data. It cleans up navi scan evaluate into readable views — average scan time by scanner, policy, and scan, plus credential coverage — and surfaces the blind and uncredentialed hosts that every other number silently depends on.
Key Capabilities
- Scan-time analysis by scanner, policy, and scan — average durations expose the slow scanner, the bloated policy, and the scan window quietly aging your data.
- Credential coverage measurement — separates hosts that scanned authenticated from those that got only a surface look — often the biggest hidden variable behind a "clean" report.
- Blind and uncredentialed host surfacing — the estate's not-seen list as a first-class output, so every downstream number carries an honest denominator.
- Trust layer for the pack — the coverage caveats that keep every other hound's claims honest all originate here.
How It Works
Chronos builds on navi scan evaluate over your local navi.db — scan timing and credential-signal data from your own Tenable scans, reorganized into views a human can act on.
Who It's For
Scan engineers tuning scanners and policies, and vulnerability management leads who want to know how much of the estate their numbers actually describe.
Proof Points
In a reference environment of 268 assets, Chronos's coverage analysis is what lets the rest of the pack say "blind and uncredentialed hosts are called out, not hidden" — the honesty line every other hound's brief depends on. Chronos measures what your scan infrastructure reports; it can flag a blind host, but it can't see through it either.
Works Better With
Chronos supplies the "we can't see this" caveat for Janus, Fenrir, and On the Scent — the difference between a finding count and a finding count you can defend in front of an auditor.