Proof the team is
getting ahead.
How fast exposures are being closed, whether closures are holding to SLA, and the validated throughput of the security team — measured against the inflow of new findings.
Throughput at a glance
The team closed 31 Fix Packs against 23 new this period — a net reduction in open exposure for the third consecutive cycle. 86% of closures met their priority-based SLA.
Mean time-to-validate for Critical items improved to 2.4 days, inside the 3-day target. The single SLA breach was a Medium-priority item awaiting a vendor patch.
Time-to-validate vs SLA, by priority
| Priority | SLA target | Mean TTV | Closed | Within SLA | Conformance |
|---|---|---|---|---|---|
| Critical | 3 days | 2.4 d | 9 | 9 / 9 | |
| High | 7 days | 5.1 d | 11 | 10 / 11 | |
| Medium | 30 days | 18.6 d | 8 | 6 / 8 | |
| Low | 90 days | 31.2 d | 3 | 3 / 3 |
TTV = time-to-validate: from Fix Pack creation to Argus-validated closure (not reported-fixed). SLA clocks start at creation.
New vs validated-closed, last 8 weeks
Open Fix Packs by age
| Age bucket | Critical | High | Medium | Low | Total | Oldest |
|---|---|---|---|---|---|---|
| 0–7 days | 2 | 5 | 9 | 6 | 22 | 6 d |
| 8–30 days | 1 | 3 | 7 | 4 | 15 | 27 d |
| 31–90 days | 0 | 1 | 2 | 3 | 6 | 71 d |
| > 90 days | 0 | 0 | 1 | 1 | 2 | 118 d |
No Critical or High item is older than 30 days. The two >90-day items are an accepted-risk EOL host and a Low-priority TLS finding scheduled for the next maintenance window.