A remediation SLA holds when its clock starts at an event you can date and its tiers follow exploitation
Pick the start of the clock
Three clocks are in common use: from detection by your scanner, from public disclosure, and from ticket creation. They can differ by weeks. A finding disclosed on a Tuesday may reach your scanner the next week and your ticket queue the week after.
Use disclosure for exposure, since attackers use disclosure. Use ticket creation only for the team that receives the work. Report both, and label them.
Tier by exploitation, not only by severity
Rapid7's Q3 2026 threat update reports 43 newly exploited high and critical vulnerabilities in the quarter, an average of three days from disclosure to exploitation, and exploitation inside 14 days for 80% and inside 30 days for 90% of the tracked set (vendor research, read 10 Nov 2026). A flat 30-day SLA covers 90% of that exploitation only after it has happened.
CISA BOD 22-01 shows a tiered model. Vulnerabilities in the Known Exploited Vulnerabilities catalog carry a default of two weeks if the CVE was assigned after 2021, and six months for older CVEs, with the default timelines open to adjustment in cases of grave risk. A private SLA can borrow the structure.
| Tier | Trigger | Example target |
|---|---|---|
| Emergency | Listed as exploited, and the asset is reachable | Mitigate within days, fix within the next change window |
| Expedited | Public exploit or active scanning reported | Fix within 14 days |
| Standard | Severe but no exploitation reported | Fix within 30 to 60 days |
| Planned | Low exposure or compensating control in place | Fix in the normal release cycle, with the control recorded |
Count the mitigation as a stop in the clock
Where a patch cannot ship in the window, a compensating control can stop the exposure while the fix waits. A SLA that counts only fixes will mark a mitigated finding as late. Write both into the policy: the finding is within SLA if exposure is blocked and the control is recorded with an expiry date.
Tenable states that patch policies can use different SLAs by criticality and exploitability. Zafran describes a workflow that opens a ServiceNow ticket, pushes a web application firewall rule and tracks the SLA. Rapid7 lists remediation projects and SLAs in its Essentials tier. These are vendor claims read on 10 Nov 2026.
Report SLA as met, mitigated or breached
Three states are more honest than two. Met means fixed inside the window. Mitigated means exposure was blocked inside the window and the fix is scheduled. Breached means neither. Report the share in each state per tier, and the age of the oldest breached item. The weekly meeting should spend its time on that last list.
NIST SP 800-40 Rev. 4 treats patching as a planned preventive maintenance process rather than an emergency each time. An SLA with named tiers is how that plan appears in a policy.
Write the exception path into the SLA
An SLA that has no exception path is broken on the first finding that cannot be fixed in time. Write the path in: who may accept the risk, for how long, on what evidence, and what ends the acceptance early.
BOD 22-01 itself requires agencies to establish internal validation and enforcement procedures. A private policy can do the same in one page: an approver by tier, a maximum acceptance period, an automatic review when a finding is added to the Known Exploited Vulnerabilities catalog, and a log the auditor can read. The exception then becomes a recorded state of the SLA, not a hole in it.
Check the SLA against one real disclosure
Test the policy on a recent case. PHP2Shell was disclosed on 21 Oct 2026 and first exploitation was observed the same day, according to the CVE record read for this site, with the CISA catalog listing following on 26 Oct 2026. Under a flat 30-day SLA the finding would not have been late until late November, after exploitation and after the catalog listing.
Under the tiers above, the finding enters the emergency tier on the day the exploitation report appears, and the clock for mitigation starts then. Run your own policy against one real case each quarter. If the SLA would have judged you on time while an attacker was already inside the window, change the tier triggers.
Related pages
- Guides
- Mean time to remediate, measured honestly
- Reading a vendor's vulnerability remediation claim
- Vulnerability ownership at scale: grouping, routing and expiry
Sources
5 sources, each with its read date
- Rapid7, Q3 2026 Threat Update, 21 Oct 2026, read 10 Nov 2026
- CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy), read 10 Nov 2026
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning, read 10 Nov 2026
- Tenable Patch Management, read 10 Nov 2026
- Rapid7 Exposure Command, read 10 Nov 2026
Last reviewed 10 Nov 2026.