The Hidden Cost Explosion
AI is exploding the volume of security findings and fixes. But every one still has to become proof: reviewed, approved, evidenced, and defensible to customers, suppliers, auditors, regulators, and insurers. The security back office was never built to scale manually at this speed.
See why security admin work is compounding.
CVE submission growth
NIST reported CVE submissions increased 263% from 2020 to 2025.vendor assessment work each week
Whistic 2025 TPRM survey: average weekly vendor-assessment work.initial assessments needing follow-up
Whistic 2025 TPRM survey: initial supplier assessments requiring follow-up.reporting clocks
NIS2 and Cyber Resilience Act reporting sequences include 24-hour early warning and 72-hour notification windows.Regulatory proof runs on clocks, not queues.
SEC, NIS2, DORA, and CRA examples turn classification, evidence, approvals, and notifications into 24-hour, 72-hour, and final-report work.
SEC
covered domestic registrants
Trigger: material cybersecurity incident materiality determination
NIS2
essential and important entities
Trigger: significant incident notification
CRA
manufacturers of products with digital elements
Trigger: corrective measure available
Legal scope varies by entity, jurisdiction, and implementing standards.
How to read this exhibit
The exhibit is about sequencing and report objects, not relative bar length.
- The trigger starts the clock.
- The report object defines what evidence has to be assembled.
- Different regimes can ask for similar facts on different timelines.
Optimization target: economic impact, not just passing proof.
Evident's trust graph should not stop when proof exists. It should ask whether proof was rejected, whether an incident created real cost, whether admin cost missed its target, and where reusable evidence can reduce the next cycle.
Sources behind the public numbers.
Public claims stay attached to the reports, regulator materials, and standards references used for the figures and clocks above.