A vulnerability remediation service-level agreement, or SLA, sets the deadline for addressing a vulnerability, names the owner, and defines the evidence needed to close the work. It should also explain how the organization handles missed deadlines and exceptions.
Consider a finding marked “critical, due in 15 days.” The owner needs to know whether that deadline covers patch deployment, a required restart, or verification across every affected system. The agreement should also name who acts if the next maintenance window falls after the deadline.
Resolve those questions in the agreement before work begins.
A useful remediation SLA gives system owners clear actions and security teams evidence they can check. The model below shows how to define those commitments and handle work that needs more time for a permanent fix.
What should a vulnerability remediation SLA include?
A vulnerability remediation SLA should identify the affected assets, required action, owner, deadline, and closure evidence. Start with the asset and finding. A Common Vulnerabilities and Exposures identifier, or CVE, identifies a vulnerability. Your team still needs to confirm where it applies and which action will address it.
Each remediation record should answer:
- Which assets and software versions are affected?
- What makes the finding urgent in this environment?
- Who owns the change, and when is it due?
- What treatment will the team apply, and how will it verify the result?
- Who can approve an exception, and when does that exception expire?
Name an owner who can act on the record. “Infrastructure” may identify a department, but someone must be responsible for scheduling a restart or resolving a failed deployment.
When work spans several teams, name one accountable remediation owner and record the dependencies separately. Preserve the original dates and history when a ticket moves between queues.
Adapt this operating model to your environment and applicable requirements. The recommendations do not prescribe a universal remediation timetable.
A remediation SLA and MTTR answer different questions
An SLA defines the time allowed for an action. Mean time to remediate, or MTTR, measures how long completed remediation work took under a stated definition.
Keep those definitions separate when setting targets.
An industry average describes the organizations and findings in a dataset. Before using it to inform your own deadlines, check the starting event, completion criteria, asset population, and reporting period. Check whether it reports a mean or median, too. The average alone cannot determine how long your business should accept a particular exposure.
Use a consistent MTTR definition in your reports. You might measure the time from the first confirmed applicable finding to verified closure, then average that duration across findings closed during the reporting period.
That calculation excludes unresolved findings. Report their age separately so an improving average does not hide an aging backlog.
To investigate delays, see Vicarius’s article on what slows critical vulnerability patching. It examines handoffs and operational bottlenecks. Use the SLA to assign responsibility for those dependencies.
Separate exposure reduction from verified closure
A team may reduce exposure before it can complete a permanent fix. Record that progress in the agreement and keep the remaining work open.
Use separate milestones for assessment, exposure reduction, and verified closure. Give exceptions their own review date.
| Milestone | Required outcome | Evidence to retain | Accountable role |
|---|---|---|---|
| Assessment | Confirm affected assets, exposure, priority, and ownership | Detection record, asset context, priority rationale | Vulnerability management lead |
| Exposure reduction | Apply a validated fix or interim mitigation | Change record, deployment result, control validation | System or application owner |
| Verified closure | Confirm the agreed closure criteria are met | Updated assessment, version or configuration evidence, validation result | Named remediation owner, with security verification |
| Exception review | Reassess unresolved exposure and approve the next action | Residual risk, control evidence, approver, expiration date | Authorized risk owner |
These milestones show whether a finding is untreated or covered by a validated interim control. They also identify the permanent-remediation work that remains.
Define each milestone before the work begins. If a mitigation satisfies an exposure-reduction target, record which assets it covers, how it works, and what limitations remain. Keep a separate deadline for permanent remediation whenever that work is still required.
How should you set remediation deadlines?
Set remediation deadlines using the affected environment, available treatment, and applicable obligations. Consider whether attackers can reach the vulnerability and what exploitation would mean for the business. Use the severity score as one input, then assign a deadline the owner can act on.
The Common Vulnerability Scoring System, or CVSS, distinguishes intrinsic vulnerability characteristics from threat and environmental factors. FIRST explains how those additional metrics refine the assessment in its CVSS v4.0 specification.
Before assigning urgency, check whether an attacker can reach the vulnerable service, whether the affected feature is enabled, and what exploitation could allow. Consider the business process that depends on the system.
Check what the treatment requires. A tested update and a configuration change may involve different execution steps. Validate any interim control separately.
Set numeric targets in your policy for the resulting priority tiers. For each tier, specify the assessment deadline, the required treatment milestone, and the escalation path. State whether the clock uses calendar hours, calendar days, or business days.
Check whether the execution plan can meet the target. If the maintenance window falls after the patching deadline, the owner needs an earlier decision on an emergency change, interim treatment, or approved exception.
Do not extend a deadline solely to make the compliance percentage look better. Record the risk decision and the operational constraint.
How to prioritize two findings with competing deadlines
Compare the findings’ exposure, exploitation evidence, business impact, and available treatment to decide which needs action first. Severity alone cannot settle that decision. Record the rationale and set separate deadlines for reducing exposure and completing verified closure.
This fictional example shows how an organization could choose deadlines. The dates are illustrative, not recommended universal SLAs. Both findings were confirmed on November 9, 2026, at 09:00 UTC.
| Decision factor | Finding A | Finding B |
|---|---|---|
| Affected service | Internet-facing service supporting customer access | Internal test service with restricted access |
| Exposure | Affected feature enabled and reachable from the internet | Access limited to a verified test-network population |
| Threat evidence | Credible exploitation evidence relevant to the finding | No exploitation evidence identified in the sources reviewed at assessment time |
| Business impact | Service disruption and unauthorized access could affect customers | Test work could be interrupted; no production dependency identified |
| Treatment | Vendor update available; compatibility testing incomplete | Supported update has passed the team’s test checks |
| Decision | Escalate for emergency handling and assess an interim control immediately | Use the approved near-term maintenance window while monitoring for changed conditions |
Finding A comes first. Its reachable attack surface, threat evidence, and customer impact justify accelerated action. The remediation owner starts the emergency change route. If a proposed temporary control is suitable, security validates its coverage and limitations. The authorized risk owner decides whether the residual exposure can remain open until the patch is ready.
In this example, the team sets an exposure-reduction target of November 9 at 17:00 UTC and a verified-closure target of November 11 at 17:00 UTC. Those targets come from the fictional organization’s policy and current assessment. The owner records what will happen if testing fails or either milestone is missed.
Finding B remains assigned. The team schedules the update for November 12 at 20:00 UTC and verification by November 13 at 10:00 UTC. The record names the implementer, service owner, and security reviewer. Restricted access lowers the assessed exposure; it does not prove the vulnerability is harmless or justify removing its deadline.
Reassess either decision if reachability changes, new exploitation evidence appears, a control fails, or a deployment is rolled back. Keep the earlier assessment and explain the change. If evidence suggests compromise, involve incident response. Patching alone cannot establish that the system is clean.
Define when each clock starts and stops
Write down the event that starts each SLA clock.
For an internal remediation target, the clock might start when the team first confirms an applicable finding on an asset. Keep the initial detection timestamp too, so the time spent checking applicability remains visible.
A contractual or regulatory obligation may use a different starting event. Track that requirement separately when necessary and retain its required trigger.
Retain timestamps for detection, applicability confirmation, owner assignment, treatment, and verification. These records show how much time each stage took.
Specify how the policy handles duplicate findings, offline assets, and reopened vulnerabilities. Reassigning a ticket should not restart its clock.
When a finding reopens, establish whether the original fix failed or a new occurrence appeared. Preserve the earlier record and explain the relationship. Otherwise, a rollback may be recorded as a fresh finding with a new deadline.
Reassess urgency when the evidence changes
A team may first identify a vulnerable application on an internal system, then discover an externally reachable instance. Reassess the original priority decision when that new exposure becomes known.
Define escalation triggers in advance. These can include new exploitation evidence, a change in reachability, or failure of an interim control. Name the person responsible for reassessing the finding and notifying the remediation owner.
The record should explain what changed, which action is now required, and whether the deadline changed. Retain the earlier decision so reviewers can reconstruct what the team knew at the time.
Vicarius’s article on time-aware vulnerability prioritization explains why priority decisions should remain tied to dated evidence.
If the evidence suggests compromise, involve incident response. Patching can address the vulnerable condition, but the team still needs to establish whether an attacker has already accessed the system.
Make exceptions expire
An exception records who accepted the remaining risk and under which conditions.
Require the requester to identify the affected assets and explain why the team cannot meet the deadline. Record the interim treatment, its validation evidence, and the exposure that remains.
The authorized risk owner should approve an expiration date or review trigger. Define how the remediation owner requests that decision.
Explain the constraint behind an exception. A phrase such as “business requirement” gives too little detail. Specify the application dependency, unresolved vendor issue, or change that needs further testing.
At review, check whether the reason for the exception still applies. Confirm whether a fix is available and whether the interim control still covers the affected systems.
If an exception expires without a new decision, escalate it. Renewal should require an explicit review.
Use an exception record with an expiry date and exit test when a fix must wait. If the risk cannot wait for the routine window, follow an emergency patching process that preserves approval and verification evidence.
Agree on closure evidence before deployment
Agree on closure criteria while planning the work, so the owner knows what evidence to collect. Settling this before deployment avoids reopening the decision afterward.
NIST SP 800-40 Rev. 4 includes verification in the enterprise patch-management process. The guidance places installation alongside identifying, prioritizing, and verifying required updates.
For a software update, closure evidence may include the installed version, completion of a required restart, and a fresh assessment. A configuration fix needs evidence that the setting changed and that the vulnerable condition no longer applies.
Verify the full affected scope. If nine servers pass validation and one is offline, keep the unresolved server in the record. Close only the assets that meet the agreed criteria.
Define what happens when validation fails. The owner may need to retry the update, investigate a dependency, or apply an approved interim treatment. Keep the failed result so the next person can see what happened.
A remediation SLA template you can use
Complete this record for each priority tier, then apply it to individual findings. Replace the bracketed fields with your organization’s decisions.
Scope: [Asset classes, environments, and finding types covered.]
Priority rule: [Evidence that places a finding in this tier, including conditions requiring escalation.]
Clock: [Starting event, calendar or business-time basis, and relevant time zone.]
Commitments: Assess within [duration]. Apply and validate the required treatment within [duration]. Complete verified closure by [deadline or policy rule].
Ownership: [Accountable remediation owner], with [security reviewer] responsible for checking the agreed evidence.
Closure evidence: [Required version, configuration, assessment, or control-validation records.]
Exception: [Authorized risk approver], [required justification], and [expiration or review trigger].
Escalation: [Recipient and action when ownership, treatment, or closure misses its target.]
Test the completed template against an overdue finding. If it leaves the change approver or closure criteria unclear, revise the relevant field.
Example: a patch delayed by compatibility testing
Suppose an internet-facing application needs an update, but testing identifies a problem with a dependent service.
The remediation owner records the blocker and proposes a temporary access restriction. Security checks whether that restriction addresses the relevant exposure and covers every affected instance.
If the restriction passes those checks, the team records the exposure-reduction milestone. The patch remains outstanding under an approved exception with a named owner and deadline.
After deployment, the team confirms the installed version and validates the affected assets. It reviews whether the temporary restriction should remain.
This workflow is illustrative. Check whether an access restriction suits the vulnerability’s exploit conditions and the system’s operational requirements. It will not be appropriate in every case.
How Vicarius connects prioritization to remediation
Vicarius’s approach to true remediation connects risk assessment, action on affected systems, and validation of the result.
vScore combines CVSS, Exploit Prediction Scoring System (EPSS), and Known Exploited Vulnerabilities (KEV) signals with asset and business context to support prioritization.
The finding determines the treatment. In Vicarius’s vulnerability remediation workflow, vPatch supports deployment on demand, on a schedule, or through policy rules. vScript supports custom remediation scripts for vulnerabilities and configuration issues.
vShield patchless protection provides memory-level protection for supported applications when a team needs protection before applying a patch.
When designing an SLA, connect each treatment decision to the affected assets, action taken, validation result, and remaining work. Use those records to track exposure reduction.
Frequently asked questions
How many days should a critical vulnerability SLA allow?
A critical vulnerability SLA needs a deadline based on applicable obligations, exploitation evidence, asset exposure, business impact, and available treatment. Severity alone cannot determine the window. Your policy should set numeric targets and specify what triggers faster action.
Does mitigation count as SLA completion?
Mitigation can count toward SLA completion if the agreement’s criteria allow it. A validated interim mitigation may satisfy an exposure-reduction milestone while permanent remediation remains open. Record the control’s scope, limitations, and next review date.
Who approves a remediation SLA exception?
The risk owner authorized by your policy should approve a remediation SLA exception. The remediation team provides the technical evidence and proposed treatment. The approval must identify who accepts the remaining risk and for how long.
Which metrics should accompany SLA compliance?
Report the age of unresolved findings, time to validated treatment, expiring exceptions, and failed or reopened remediations. Use consistent measurement boundaries so teams can compare results and identify where to intervene.
Put the agreement to work
Choose one overdue finding and follow it through your process. Identify its owner, the treatment decision, and the evidence required for closure.
Use that finding to discuss where your team’s remediation workflow needs to change.
Request a personalized vRx demo to see how Vicarius’s prioritization, patching, scripting, and patchless protection could fit your environment.








































































.webp)
































