building-vulnerability-aging-and-sla-tracking

Calculates vulnerability aging, SLA compliance, MTTR, and escalation lists from scan data.

4|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/braydos-h/BreachPilot --skill building-vulnerability-aging-and-sla-tracking-braydos-h
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: building-vulnerability-aging-and-sla-tracking
Source: https://github.com/braydos-h/BreachPilot/tree/main/skills/building-vulnerability-aging-and-sla-tracking
Command: npx skills add https://github.com/braydos-h/BreachPilot --skill building-vulnerability-aging-and-sla-tracking-braydos-h

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Security teams struggle to measure how long vulnerabilities remain unpatched and whether remediation meets severity-based deadlines, leaving overdue risks invisible and accountability unclear. ## Core Features & Use Cases - Aging and SLA Calculation: Computes age in days, SLA deadlines, overdue status, and percent-of-SLA elapsed for each vulnerability from CSV scan data using pandas. - KPI Dashboards and Escalations: Generates MTTR by severity, SLA compliance rates, aging distribution buckets, and tiered escalation lists (owner reminder through VP/CTO escalation). - Use Case: Export vulnerabilities from Tenable or Qualys into a CSV, then run the tracker to produce a monthly aging report showing overdue critical findings and the escalation list for the security committee. ## Quick Start Ask the assistant to run the SLA tracking script against your vulnerability CSV export and generate the aging report, KPI summary, and escalation list.

Frequently Asked Questions about building-vulnerability-aging-and-sla-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track vulnerability SLA compliance from scan data?▼

Export vulnerabilities to CSV with discovery_date, severity, and remediation_date columns, then run the process.py script with the analyze or kpis command. It calculates age in days, SLA deadlines per severity, overdue status, and compliance rates using pandas.

What SLA timelines should I use for vulnerability remediation?▼

The skill's standard framework sets 14 days for Critical, 30 for High, 60 for Medium, and 90 for Low severity. Adaptive modifiers shorten SLAs for internet-facing assets, CISA KEV listings, and high EPSS scores, while compensating controls can extend them.

How is MTTR calculated for vulnerabilities?▼

MTTR is the mean of remediation_date minus discovery_date across closed vulnerabilities, computed overall and per severity. The agent.py script also reports median days and sample counts per severity level.

Does this work with Tenable or Qualys scan exports?▼

Yes, the references document Tenable.io and Qualys API endpoints for exporting vulnerability data. You transform those exports into the expected CSV columns (severity, discovery_date, remediation_date) before running the aging analysis.

When should vulnerability SLA exceptions be allowed?▼

Exceptions apply when vendor patches are unavailable or compensating controls reduce risk, but they require documented business justification and CISO approval for Critical or High findings. The framework caps extensions at 90 days with one renewal.