Skip to content
Get packs

Vulnerability Aging and SLA Tracking

Track how long vulnerabilities stay open and whether fixes meet severity-based deadlines.

Source Download skill
Repository
mukul975/Anthropic-Cybersecurity-Skills
Stars
35,430
Licence
Apache-2.0
Files
7 files

What it does

Once installed, the agent helps design a remediation policy with deadlines by severity (for example 14 days for critical, 30 for high, 60 for medium, 90 for low), then builds logic to measure how long each vulnerability has been open, flag overdue items, and trigger escalation steps as deadlines approach. It can also produce compliance KPIs such as mean time to remediate and SLA compliance rate for dashboards or reports. Its bundled Python scripts can process a CSV export of vulnerability data and output aging reports and escalation lists.

Great for

  • Security or vulnerability management teams setting up SLA policies and aging dashboards
  • Engineers who need Python code to calculate vulnerability age and overdue status from scan data
  • Teams preparing evidence of remediation timelines for audits or compliance reviews

Skip it if

  • Organizations without a vulnerability scanner or ticketing data: the scripts expect a CSV with discovery and remediation dates and severity, so the output is meaningless without real inputs
  • Anyone expecting a turnkey product: the scripts use hardcoded SLA values that differ between the SKILL.md and scripts/agent.py, so they must be reviewed and aligned to your own policy before use

Try asking

  • “Build a vulnerability aging dashboard that shows open items by age bucket and severity”
  • “Write a script that reads a scanner CSV export and lists overdue critical and high vulnerabilities”
  • “Draft an SLA policy with severity deadlines and an escalation path for overdue findings”
  • “Calculate MTTR and SLA compliance rate for a monthly security committee report”
Step-by-step guide: how to use Vulnerability Aging and SLA TrackingInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 7 original files, the Apache-2.0 licence and an attribution note.

    building-vulnerability-aging-and-sla-tracking.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip building-vulnerability-aging-and-sla-tracking.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip building-vulnerability-aging-and-sla-tracking.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Review and reconcile the SLA numbers in SKILL.md, agent.py and process.py before using them, since they differ (for example critical is 14 days in one place and 7 in another)
  • Run the scripts on a copy of your data first and check the age calculations, especially how open items are aged against today's date
  • Ask the agent to adapt the SLA values and escalation thresholds to your organization's written policy rather than using the defaults

What's inside

  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py
  • SKILL.md

Redistributed unmodified from mukul975/Anthropic-Cybersecurity-Skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.