Remediation SLA in practice
SLAs make mobilization measurable. They work when both security and system owners agreed to them in advance, when the clock start is defined, and when exceptions have an owner and an expiry date. An SLA set by security alone gets ignored; one tied to business tiers gets budget. Publish the tiers, the clocks and the exception process in one short document.
Federal practice now ties clocks to exploitation evidence and exposure. Under BOD 26-04, timelines begin when CISA adds a flaw to KEV or when the agency identifies it on an asset, and removing an asset from public exposure can lengthen the allowed time. Private programs copy this shape: tight clocks for exploited, exposed flaws on critical assets, longer ones elsewhere.
An example
CISA's BOD 26-04 (June 10, 2026) requires agencies to remediate within its Table 1 timelines by Phase III, 180 days after issuance, and revokes BOD 19-02 and BOD 22-01.
Source, read 12 Nov 2026.
Related terms
- Mean time to remediate (MTTR)
- CISA Known Exploited Vulnerabilities (KEV) catalog
- Mobilization (CTEM stage 5)
- Exposure backlog
Sources
Last reviewed 12 Nov 2026.