building-vulnerability-aging-and-sla-tracking

name	building-vulnerability-aging-and-sla-tracking
description	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.
domain	cybersecurity
subdomain	vulnerability-management
tags	["vulnerability-management","sla-tracking","remediation-metrics","aging-report","kpi","compliance","risk-management"]
version	1.0
author	mahipal
license	Apache-2.0
nist_csf	["ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06"]
mitre_attack	["T1190","T1203","T1068"]

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