What Is Vulnerability Remediation SLA?
A vulnerability remediation SLA is the maximum time a team commits to fixing a security finding, usually set by severity, such as days for criticals and months for low-risk issues. It turns a vulnerability policy into a deadline each finding can be measured against.
Also known as:
How Remediation SLAs Are Set
Most SLAs start from severity and then adjust for context. A common pattern gives critical findings the shortest window, high findings a longer one and medium or low findings the longest, with tighter deadlines for vulnerabilities that are actively exploited or on internet-facing systems. Customer contracts, compliance audits and internal risk appetite all shape the final numbers.
A Public Example of Risk-Based Timelines
CISA's BOD 26-04, issued in June 2026, sets remediation timelines for US federal civilian agencies based on four questions: is the asset publicly exposed, is the vulnerability in the Known Exploited Vulnerabilities catalog, can an attacker automate the exploit, and does exploitation give partial or total control. Timelines range from 3 days, with forensic triage in the worst cases, to 14 days, 60 days or the next scheduled system upgrade. It is a useful model for any team moving from severity-only SLAs to risk-based ones.
What an SLA Policy Should Define
- Start and stop points. When the clock starts (detection, triage or disclosure) and what counts as fixed.
- Severity and context. Which inputs set the deadline, such as CVSS, exploitation status and exposure.
- Owners. Who is accountable for each finding, so the deadline has a name on it.
- Exceptions. How risk acceptance and compensating controls are approved and recorded.
- Escalation. What happens, and who is told, when a finding is about to breach.
Why SLAs Get Missed
SLAs slip when the backlog is full of findings that are not real, when owners are unclear and when fixes stall in review or CI. Tracking SLA compliance alongside mean time to remediate (MTTR) shows whether the program is meeting its deadlines or only improving the average.
How Nullify Keeps Findings Inside SLA
Nullify moves actively exploited vulnerabilities and zero-days affecting your stack to the top of the backlog, writes and validates fixes before review and routes them to the right owner. Stalled security PRs and tickets are escalated through Slack with the risk and SLA stated, and reports show MTTR and SLA compliance per team. See how Nullify runs your security program.
Key Takeaways
- A remediation SLA is the deadline for fixing a finding, usually set by severity.
- Risk-based SLAs also weigh exploitation status and exposure, as CISA's BOD 26-04 does.
- A good policy defines start and stop points, owners, exceptions and escalation.
- Track SLA compliance alongside MTTR to see whether deadlines are actually met.
Read More About Vulnerability Remediation SLA
Reduce MTTR
See Nullify in Action
Nullify escalates stalled fixes before the SLA slips and reports compliance per team.