TL;DR: How many vulnerabilities have appeared since the last assessment is what Exposure Clock measures, with Hadrian reporting the shift from snapshot-style pentest output to exposure velocity. Validation cycles need to track change faster, or risk reduction claims can lag behind the live attack surface.
Editorial analysis by NHI Mgmt Group, based on content published by Hadrian: “Vulnerability Disclosure Trends and Exposure Velocity”.
Key questions
Q: Why does exposure velocity matter more than point-in-time vulnerability counts?
A: Exposure velocity matters because risk changes as new assets, services, and misconfigurations appear after an assessment.
Q: When does a pentest become too stale to be useful?
A: A pentest becomes stale when the tested configuration no longer resembles the live environment, especially after deployments, access changes, or infrastructure drift.
Q: How should teams handle vulnerabilities that appear between scheduled pentests?
A: Treat them as evidence that the assessment model is behind the environment.
Practitioner guidance
- Track exposure velocity alongside severity Measure how many new vulnerabilities and exposed assets appear between assessments, then trend that number by environment and business service.
- Shorten the window between change and validation Re-run exposure checks after infrastructure changes, application releases, and policy exceptions so drift is caught before it compounds.
- Prioritise recurring exposure patterns Escalate issues that reappear across multiple scans or assessments, because repetition signals a broken control process rather than an isolated flaw.
Bottom line: Exposure management weakens when teams treat vulnerability assessment as a snapshot instead of a moving target.
Glossary terms: Exposure Reduction Velocity, Pentest Drift, Continuous validation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Exposure velocity is now a governance metric, not just an operational curiosity. When exposure changes faster than assessment cadence, vulnerability management stops being a list of findings and becomes a measurement problem. The useful question is whether the programme can see newly exposed assets and services before attackers do, not whether last quarter's pentest was complete. Practitioners should treat change rate as a first-class risk indicator.
A question worth separating out:
Q: When should organisations move from quarterly testing to continuous validation?
A: When applications change faster than assessments can keep up. If microservices, APIs, serverless functions, or mobile releases are landing frequently, quarterly testing leaves long unvalidated windows. Continuous validation becomes necessary once the gap between releases and tests is large enough to make previous results unreliable.
👉 Read our full editorial: Exposure velocity is reshaping vulnerability management priorities