Building Vulnerability Aging and SLA Tracking
Overview
With over 30,000 new vulnerabilities identified in 2024 (a 17% increase from the prior year), organizations must track how long vulnerabilities remain unpatched and whether remediation occurs within defined Service Level Agreements (SLAs). Vulnerability aging measures the time between discovery and remediation, while SLA tracking enforces severity-based deadlines. Industry benchmarks indicate standard SLAs of 14 days for critical, 30 days for high, 60 days for medium, and 90 days for low vulnerabilities, though more aggressive timelines (24-48 hours for actively exploited critical CVEs) are increasingly common. This skill covers designing SLA policies, building aging dashboards, implementing automated escalations, and generating compliance metrics.
When to Use
- When deploying or configuring building vulnerability aging and sla tracking capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- Vulnerability management platform with historical scan data
- Asset inventory with criticality ratings
- ITSM/ticketing system for remediation tracking
- Reporting platform (Splunk, Elastic, Power BI, Grafana)
- Stakeholder agreement on SLA timelines and escalation procedures
Core Concepts
Standard Vulnerability SLA Framework
| Severity |
CVSS Range |
Standard SLA |
Aggressive SLA |
CISA KEV SLA |
| Critical |
9.0-10.0 |
14 days |
48 hours |
BOD 22-01 due date |
| High |
7.0-8.9 |
30 days |
7 days |
14 days |
| Medium |
4.0-6.9 |
60 days |
30 days |
N/A |
| Low |
0.1-3.9 |
90 days |
60 days |
N/A |
| Informational |
0.0 |
Best effort |
Best effort |
N/A |
Adaptive SLA Modifiers
| Factor |
Modifier |
Rationale |
| Internet-facing asset |
-50% SLA |
Higher exposure risk |
| CISA KEV listed |
Override to 48h |
Active exploitation confirmed |
| EPSS > 0.7 |
-50% SLA |
High exploitation probability |
| Tier 1 (crown jewel) asset |
-25% SLA |
Maximum business impact |
| Compensating control in place |
+25% SLA |
Risk partially mitigated |
| Vendor patch unavailable |
Exception with review date |
Cannot remediate yet |
Key Performance Indicators (KPIs)
| KPI |
Formula |
Target |
| Mean Time to Remediate (MTTR) |
Avg(remediation_date - discovery_date) |
< 30 days overall |
| SLA Compliance Rate |
(Vulns remediated within SLA / Total vulns) * 100 |
>= 90% |
| Overdue Vulnerability Count |
Count where age > SLA |
Trending downward |
| Vulnerability Aging Distribution |
Count by age bucket (0-14d, 15-30d, 31-60d, 60+d) |
Majority in 0-30d |
| Remediation Velocity |
Vulns closed per week |
Trending upward |
| Exception Rate |
(Exceptions / Total vulns) * 100 |
< 5% |
Workflow
Step 1: Define SLA Policy Document
Vulnerability Remediation SLA Policy v1.0
1. Scope: All information systems and applications
2. Severity Classification: Based on CVSS v4.0/v3.1 base score
3. SLA Timelines: See Standard SLA Framework table
4. Adaptive Modifiers: Applied based on asset context
5. Exception Process:
- Must be documented with business justification
- Requires compensating control description
- Maximum extension: 90 days (one renewal)
- CISO approval required for Critical/High exceptions
6. Escalation Path:
- 50% SLA elapsed: Automated reminder to asset owner
- 75% SLA elapsed: Escalation to manager
- 100% SLA elapsed (overdue): CISO notification
- 120% SLA elapsed: VP/CTO escalation
7. Metrics Reporting: Monthly to security committee
Step 2: Build the Aging Calculation Engine
import pandas as pd
from datetime import datetime, timedelta
class VulnerabilityAgingTracker:
"""Track vulnerability aging and SLA compliance."""
SLA_DAYS = {
"Critical": 14,
"High": 30,
"Medium": 60,
"Low": 90,
}
def __init__(self, sla_overrides=None):
if sla_overrides:
self.SLA_DAYS.update(sla_overrides)
def calculate_aging(self, vulns_df):
"""Calculate aging metrics for each vulnerability."""
today = datetime.now()
vulns_df["discovery_date"] = pd.to_datetime(vulns_df["discovery_date"])
vulns_df["remediation_date"] = pd.to_datetime(
vulns_df["remediation_date"], errors="coerce"
)
vulns_df["age_days"] = vulns_df.apply(
lambda row: (row["remediation_date"] - row["discovery_date"]).days
if pd.notna(row["remediation_date"])
else (today - row["discovery_date"]).days,
axis=1
)
vulns_df["sla_days"] = vulns_df["severity"].map(self.SLA_DAYS)
vulns_df["sla_deadline"] = vulns_df["discovery_date"] + \
pd.to_timedelta(vulns_df["sla_days"], unit="D")
vulns_df["is_overdue"] = vulns_df.apply(
lambda row: row["age_days"] > row["sla_days"]
if pd.isna(row["remediation_date"]) else False,
axis=1
)
vulns_df["sla_compliance"] = vulns_df.apply(
lambda row: row["age_days"] <= row["sla_days"]
if pd.notna(row["remediation_date"]) else None,
axis=1
)
vulns_df["days_overdue"] = vulns_df.apply(
lambda row: max(0, row["age_days"] - row["sla_days"])
if row["is_overdue"] else 0,
axis=1
)
vulns_df["sla_pct_elapsed"] = (
vulns_df["age_days"] / vulns_df["sla_days"] * 100
).round(1)
return vulns_df
def generate_kpis(self, vulns_df):
"""Generate KPI summary from aging data."""
open_vulns = vulns_df[vulns_df["remediation_date"].isna()]
closed_vulns = vulns_df[vulns_df["remediation_date"].notna()]
kpis = {
"total_vulnerabilities": len(vulns_df),
"open_vulnerabilities": len(open_vulns),
"closed_vulnerabilities": len(closed_vulns),
"overdue_count": open_vulns["is_overdue"].sum(),
"mttr_days": closed_vulns["age_days"].mean() if len(closed_vulns) > 0 else 0,
"sla_compliance_rate": (
closed_vulns["sla_compliance"].mean() * 100
if len(closed_vulns) > 0 else 0
),
}
kpis["overdue_by_severity"] = (
open_vulns[open_vulns["is_overdue"]]
.groupby("severity")
.size()
.to_dict()
)
return kpis
def get_escalation_list(self, vulns_df):
"""Get vulnerabilities requiring escalation."""
open_vulns = vulns_df[vulns_df["remediation_date"].isna()].copy()
escalations = []
for _, vuln in open_vulns.iterrows():
pct = vuln["sla_pct_elapsed"]
if pct >= 120:
level = "VP/CTO Escalation"
elif pct >= 100:
level = "CISO Notification"
elif pct >= 75:
level = "Manager Escalation"
elif pct >= 50:
level = "Owner Reminder"
else:
continue
escalations.append({
"cve_id": vuln.get("cve_id", ""),
"severity": vuln["severity"],
"age_days": vuln["age_days"],
"sla_days": vuln["sla_days"],
"days_overdue": vuln["days_overdue"],
"sla_pct": pct,
"escalation_level": level,
"asset": vuln.get("asset", ""),
"owner": vuln.get("owner", ""),
})
return pd.DataFrame(escalations)
Step 3: Dashboard Visualization
# Grafana/Kibana query examples for vulnerability aging
# Age distribution histogram (Elasticsearch)
age_distribution_query = {
"aggs": {
"age_buckets": {
"range": {
"field": "age_days",
"ranges": [
{"key": "0-7 days", "to": 8},
{"key": "8-14 days", "from": 8, "to": 15},
{"key": "15-30 days", "from": 15, "to": 31},
{"key": "31-60 days", "from": 31, "to": 61},
{"key": "61-90 days", "from": 61, "to": 91},
{"key": "90+ days", "from": 91},
]
}
}
}
}
# SLA compliance trend (monthly)
sla_trend_query = {
"aggs": {
"monthly": {
"date_histogram": {"field": "remediation_date", "interval": "month"},
"aggs": {
"within_sla": {
"filter": {"script": {
"source": "doc['age_days'].value <= doc['sla_days'].value"
}}
}
}
}
}
}
Best Practices
- Start with achievable SLA targets and tighten them as processes mature
- Adapt SLAs based on asset criticality and threat context, not just CVSS scores
- Automate escalation notifications to reduce manual tracking overhead
- Track MTTR trends month-over-month to demonstrate improvement
- Build exception workflows that require documented compensating controls
- Report SLA compliance to executive leadership monthly for accountability
- Include aging metrics in security committee and board-level reporting
- Integrate SLA tracking with ITSM ticketing for end-to-end remediation visibility
Common Pitfalls
- Setting unrealistic SLA targets that teams cannot meet, causing SLA fatigue
- Not adapting SLAs for asset criticality, treating all systems equally
- Lacking exception processes, forcing teams to either ignore SLAs or request blanket waivers
- Measuring only open vulnerability count without considering age and SLA compliance
- Not tracking the SLA clock from discovery date (using report date instead)
- Failing to re-baseline SLAs as team maturity improves
Related Skills
- implementing-vulnerability-remediation-sla
- building-executive-vulnerability-risk-report
- implementing-security-metrics-and-kpis
- performing-remediation-validation-scanning
1---2name: building-vulnerability-aging-and-sla-tracking3description: Implement a vulnerability aging dashboard and SLA tracking system that measures time-to-remediation against severity-based deadlines (e.g. 14 days critical, 30 days high, 60 days medium, 90 days low), with automated escalations and compliance metrics reporting. Use when designing SLA policies, building aging/remediation dashboards, or proving compliance with remediation timelines.4domain: cybersecurity5subdomain: vulnerability-management6tags:7- vulnerability-management8- sla-tracking9- remediation-metrics10- aging-report11- kpi12- compliance13- risk-management14version: '1.0'15author: mahipal16license: Apache-2.017nist_csf:18- ID.RA-0119- ID.RA-0220- ID.IM-0221- ID.RA-0622mitre_attack:23- T119024- T120325- T106826metadata:27 source: https://skillmd.com/skills/26zl/building-vulnerability-aging-and-sla-tracking28---2930# Building Vulnerability Aging and SLA Tracking3132## Overview33With over 30,000 new vulnerabilities identified in 2024 (a 17% increase from the prior year), organizations must track how long vulnerabilities remain unpatched and whether remediation occurs within defined Service Level Agreements (SLAs). Vulnerability aging measures the time between discovery and remediation, while SLA tracking enforces severity-based deadlines. Industry benchmarks indicate standard SLAs of 14 days for critical, 30 days for high, 60 days for medium, and 90 days for low vulnerabilities, though more aggressive timelines (24-48 hours for actively exploited critical CVEs) are increasingly common. This skill covers designing SLA policies, building aging dashboards, implementing automated escalations, and generating compliance metrics.343536## When to Use3738- When deploying or configuring building vulnerability aging and sla tracking capabilities in your environment39- When establishing security controls aligned to compliance requirements40- When building or improving security architecture for this domain41- When conducting security assessments that require this implementation4243## Prerequisites44- Vulnerability management platform with historical scan data45- Asset inventory with criticality ratings46- ITSM/ticketing system for remediation tracking47- Reporting platform (Splunk, Elastic, Power BI, Grafana)48- Stakeholder agreement on SLA timelines and escalation procedures4950## Core Concepts5152### Standard Vulnerability SLA Framework5354| Severity | CVSS Range | Standard SLA | Aggressive SLA | CISA KEV SLA |55|----------|-----------|-------------|----------------|-------------|56| Critical | 9.0-10.0 | 14 days | 48 hours | BOD 22-01 due date |57| High | 7.0-8.9 | 30 days | 7 days | 14 days |58| Medium | 4.0-6.9 | 60 days | 30 days | N/A |59| Low | 0.1-3.9 | 90 days | 60 days | N/A |60| Informational | 0.0 | Best effort | Best effort | N/A |6162### Adaptive SLA Modifiers6364| Factor | Modifier | Rationale |65|--------|----------|-----------|66| Internet-facing asset | -50% SLA | Higher exposure risk |67| CISA KEV listed | Override to 48h | Active exploitation confirmed |68| EPSS > 0.7 | -50% SLA | High exploitation probability |69| Tier 1 (crown jewel) asset | -25% SLA | Maximum business impact |70| Compensating control in place | +25% SLA | Risk partially mitigated |71| Vendor patch unavailable | Exception with review date | Cannot remediate yet |7273### Key Performance Indicators (KPIs)7475| KPI | Formula | Target |76|-----|---------|--------|77| Mean Time to Remediate (MTTR) | Avg(remediation_date - discovery_date) | < 30 days overall |78| SLA Compliance Rate | (Vulns remediated within SLA / Total vulns) * 100 | >= 90% |79| Overdue Vulnerability Count | Count where age > SLA | Trending downward |80| Vulnerability Aging Distribution | Count by age bucket (0-14d, 15-30d, 31-60d, 60+d) | Majority in 0-30d |81| Remediation Velocity | Vulns closed per week | Trending upward |82| Exception Rate | (Exceptions / Total vulns) * 100 | < 5% |8384## Workflow8586### Step 1: Define SLA Policy Document8788```89Vulnerability Remediation SLA Policy v1.090911. Scope: All information systems and applications922. Severity Classification: Based on CVSS v4.0/v3.1 base score933. SLA Timelines: See Standard SLA Framework table944. Adaptive Modifiers: Applied based on asset context955. Exception Process:96 - Must be documented with business justification97 - Requires compensating control description98 - Maximum extension: 90 days (one renewal)99 - CISO approval required for Critical/High exceptions1006. Escalation Path:101 - 50% SLA elapsed: Automated reminder to asset owner102 - 75% SLA elapsed: Escalation to manager103 - 100% SLA elapsed (overdue): CISO notification104 - 120% SLA elapsed: VP/CTO escalation1057. Metrics Reporting: Monthly to security committee106```107108### Step 2: Build the Aging Calculation Engine109110```python111import pandas as pd112from datetime import datetime, timedelta113114class VulnerabilityAgingTracker:115 """Track vulnerability aging and SLA compliance."""116117 SLA_DAYS = {118 "Critical": 14,119 "High": 30,120 "Medium": 60,121 "Low": 90,122 }123124 def __init__(self, sla_overrides=None):125 if sla_overrides:126 self.SLA_DAYS.update(sla_overrides)127128 def calculate_aging(self, vulns_df):129 """Calculate aging metrics for each vulnerability."""130 today = datetime.now()131132 vulns_df["discovery_date"] = pd.to_datetime(vulns_df["discovery_date"])133 vulns_df["remediation_date"] = pd.to_datetime(134 vulns_df["remediation_date"], errors="coerce"135 )136137 vulns_df["age_days"] = vulns_df.apply(138 lambda row: (row["remediation_date"] - row["discovery_date"]).days139 if pd.notna(row["remediation_date"])140 else (today - row["discovery_date"]).days,141 axis=1142 )143144 vulns_df["sla_days"] = vulns_df["severity"].map(self.SLA_DAYS)145 vulns_df["sla_deadline"] = vulns_df["discovery_date"] + \146 pd.to_timedelta(vulns_df["sla_days"], unit="D")147148 vulns_df["is_overdue"] = vulns_df.apply(149 lambda row: row["age_days"] > row["sla_days"]150 if pd.isna(row["remediation_date"]) else False,151 axis=1152 )153154 vulns_df["sla_compliance"] = vulns_df.apply(155 lambda row: row["age_days"] <= row["sla_days"]156 if pd.notna(row["remediation_date"]) else None,157 axis=1158 )159160 vulns_df["days_overdue"] = vulns_df.apply(161 lambda row: max(0, row["age_days"] - row["sla_days"])162 if row["is_overdue"] else 0,163 axis=1164 )165166 vulns_df["sla_pct_elapsed"] = (167 vulns_df["age_days"] / vulns_df["sla_days"] * 100168 ).round(1)169170 return vulns_df171172 def generate_kpis(self, vulns_df):173 """Generate KPI summary from aging data."""174 open_vulns = vulns_df[vulns_df["remediation_date"].isna()]175 closed_vulns = vulns_df[vulns_df["remediation_date"].notna()]176177 kpis = {178 "total_vulnerabilities": len(vulns_df),179 "open_vulnerabilities": len(open_vulns),180 "closed_vulnerabilities": len(closed_vulns),181 "overdue_count": open_vulns["is_overdue"].sum(),182 "mttr_days": closed_vulns["age_days"].mean() if len(closed_vulns) > 0 else 0,183 "sla_compliance_rate": (184 closed_vulns["sla_compliance"].mean() * 100185 if len(closed_vulns) > 0 else 0186 ),187 }188189 kpis["overdue_by_severity"] = (190 open_vulns[open_vulns["is_overdue"]]191 .groupby("severity")192 .size()193 .to_dict()194 )195196 return kpis197198 def get_escalation_list(self, vulns_df):199 """Get vulnerabilities requiring escalation."""200 open_vulns = vulns_df[vulns_df["remediation_date"].isna()].copy()201202 escalations = []203 for _, vuln in open_vulns.iterrows():204 pct = vuln["sla_pct_elapsed"]205 if pct >= 120:206 level = "VP/CTO Escalation"207 elif pct >= 100:208 level = "CISO Notification"209 elif pct >= 75:210 level = "Manager Escalation"211 elif pct >= 50:212 level = "Owner Reminder"213 else:214 continue215216 escalations.append({217 "cve_id": vuln.get("cve_id", ""),218 "severity": vuln["severity"],219 "age_days": vuln["age_days"],220 "sla_days": vuln["sla_days"],221 "days_overdue": vuln["days_overdue"],222 "sla_pct": pct,223 "escalation_level": level,224 "asset": vuln.get("asset", ""),225 "owner": vuln.get("owner", ""),226 })227228 return pd.DataFrame(escalations)229```230231### Step 3: Dashboard Visualization232233```python234# Grafana/Kibana query examples for vulnerability aging235236# Age distribution histogram (Elasticsearch)237age_distribution_query = {238 "aggs": {239 "age_buckets": {240 "range": {241 "field": "age_days",242 "ranges": [243 {"key": "0-7 days", "to": 8},244 {"key": "8-14 days", "from": 8, "to": 15},245 {"key": "15-30 days", "from": 15, "to": 31},246 {"key": "31-60 days", "from": 31, "to": 61},247 {"key": "61-90 days", "from": 61, "to": 91},248 {"key": "90+ days", "from": 91},249 ]250 }251 }252 }253}254255# SLA compliance trend (monthly)256sla_trend_query = {257 "aggs": {258 "monthly": {259 "date_histogram": {"field": "remediation_date", "interval": "month"},260 "aggs": {261 "within_sla": {262 "filter": {"script": {263 "source": "doc['age_days'].value <= doc['sla_days'].value"264 }}265 }266 }267 }268 }269}270```271272## Best Practices2731. Start with achievable SLA targets and tighten them as processes mature2742. Adapt SLAs based on asset criticality and threat context, not just CVSS scores2753. Automate escalation notifications to reduce manual tracking overhead2764. Track MTTR trends month-over-month to demonstrate improvement2775. Build exception workflows that require documented compensating controls2786. Report SLA compliance to executive leadership monthly for accountability2797. Include aging metrics in security committee and board-level reporting2808. Integrate SLA tracking with ITSM ticketing for end-to-end remediation visibility281282## Common Pitfalls283- Setting unrealistic SLA targets that teams cannot meet, causing SLA fatigue284- Not adapting SLAs for asset criticality, treating all systems equally285- Lacking exception processes, forcing teams to either ignore SLAs or request blanket waivers286- Measuring only open vulnerability count without considering age and SLA compliance287- Not tracking the SLA clock from discovery date (using report date instead)288- Failing to re-baseline SLAs as team maturity improves289290## Related Skills291- implementing-vulnerability-remediation-sla292- building-executive-vulnerability-risk-report293- implementing-security-metrics-and-kpis294- performing-remediation-validation-scanning