A vulnerability dashboard can contain accurate numbers and still create the wrong behaviour. Metrics should help leaders understand coverage, priority, delivery and residual exposure. Raw totals rarely do that on their own.
Start with coverage
- Known assets assessed
- Authenticated scan coverage
- Internet-facing asset coverage
- Cloud account and subscription coverage
- Assets with a named owner
A falling vulnerability count is not reassuring if half the estate is not being assessed.
Measure priority and ageing
- Known exploited vulnerabilities by age
- Internet-facing high-priority exposures
- Vulnerabilities beyond agreed treatment time
- Median and percentile time to remediate
- Age of risk acceptances and exceptions
Use medians and percentiles alongside averages. A small group of very old exposures can disappear inside a single mean value.
Measure flow and outcomes
- New versus closed exposures
- Remediation rate and backlog growth
- Reopened vulnerabilities
- Patch or mitigation validation success
- Recurrence by technology or root cause
- Material attack paths removed
Metrics to challenge
Total vulnerability count, critical count, average CVSS and percentage patched can all mislead when presented without asset population, exposure and trend. They are supporting measures, not executive outcomes.
Build a reporting hierarchy
Operational teams need asset-level actions and ownership. Service leaders need trend, ageing and blockers. Executives need material exposure, control confidence, decisions required and whether risk is reducing. Do not force one dashboard to serve all three audiences.
Every metric should answer one of three questions: Are we looking in the right places? Are we acting on the right things? Is exposure actually reducing?