Vulnerability Age and Remediation SLAs
What You'll Learn
You'll learn how to establish time-based remediation targets that balance severity ratings, asset criticality, and organizational risk appetite to ensure timely patching without overwhelming resources.
Understanding Remediation SLAs
After prioritizing vulnerabilities using risk-based frameworks (CVSS, EPSS, SSVC) and asset criticality, you need time-bound commitments: Service Level Agreements (SLAs) that dictate when patches must be deployed.
Vulnerability age—the time elapsed since a vulnerability was discovered in your environment—directly correlates with attacker opportunity. The longer a vulnerability exists, the greater the window for exploitation. Remediation SLAs create accountability and urgency.
Setting Effective SLAs
Your SLAs should reflect severity, exploitability, and business impact:
Common SLA framework example:
- Critical vulnerabilities (CVSS 9.0-10.0, actively exploited): 7 days
- High vulnerabilities (CVSS 7.0-8.9): 30 days
- Medium vulnerabilities (CVSS 4.0-6.9): 90 days
- Low vulnerabilities (CVSS 0.1-3.9): 180 days or next maintenance window
These timelines should adjust based on threat intelligence integration—if EPSS predicts active exploitation or you detect in-the-wild attacks, escalate the SLA. Similarly, vulnerabilities on internet-facing or business-critical assets deserve faster timelines.
The Balancing Act
Think of SLAs like triage in an emergency room: life-threatening conditions get immediate attention, while minor issues wait. Your organization's risk tolerance determines how aggressive these timelines are—a financial services company might remediate critical vulnerabilities in 48 hours, while a research lab might allow 14 days.
Track SLA compliance rates as a key metric. Consistent misses signal resource constraints, prioritization problems, or unrealistic targets.
Key Takeaway: Vulnerability age and remediation SLAs transform risk prioritization into actionable timelines, ensuring high-risk exposures are addressed before attackers can weaponize them, while balancing operational capacity and business continuity requirements.