New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Implementing Vulnerability Remediation Sla

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation…

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Implementing Vulnerability Remediation Sla

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-vulnerability-remediation-sla -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-vulnerability-remediation-sla --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-vulnerability-remediation-sla .claude/skills/implementing-vulnerability-remediation-sla && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implementing-vulnerability-remediation-sla
GitHub stars
34k
Token cost
~1.9k tokens
SKILL.md length
632 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation…

  • Works in 5 steps: Define Asset Tiers → Establish SLA Policy Document → Integrate with Ticketing System → …
  • Defining mandatory patching timeframes by severity and asset criticality
  • SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 5 more sections
  • Runs Python scripts from its folder

What it does

Implementing Vulnerability Remediation Sla is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation KPIs/trending metrics. Use when defining mandatory patching timeframes by severity and asset criticality, building an SLA policy document, or setting up escalation and KPI tracking for vulnerability remediation.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).

It sits in Business, Finance & HR, covering OKRs and executive reporting. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Defining mandatory patching timeframes by severity and asset criticality
  • Building an SLA policy document
  • Setting up escalation and KPI tracking for vulnerability remediation

Example prompts

  • “/implementing-vulnerability-remediation-sla”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Define Asset Tiers
  2. Establish SLA Policy Document
  3. Integrate with Ticketing System
  4. Configure Escalation Chain
  5. Establish Exception Process

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implementing Vulnerability Remediation Sla loads about 1.9k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 632 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 632 words, ~1,871 tokens.

Download SKILL.mdSave it as .claude/skills/implementing-vulnerability-remediation-sla/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
implementing-vulnerability-remediation-sla
description
Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation KPIs/trending metrics. Use when defining mandatory patching timeframes by severity and asset criticality, building an SLA policy document, or setting up escalation and KPI tracking for vulnerability remediation.
domain
cybersecurity
subdomain
vulnerability-management
tags
vulnerability-management, cve, sla, remediation, patch-management, risk
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

Implementing Vulnerability Remediation SLA

Overview

Vulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs drive accountability, ensure consistent remediation timelines, and provide measurable KPIs for vulnerability management maturity.

When to Use

  • When deploying or configuring implementing vulnerability remediation sla 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 scanning program producing regular findings
  • Asset inventory with criticality classifications
  • Ticketing system (Jira, ServiceNow, etc.) for remediation tracking
  • Executive sponsorship for SLA enforcement
  • Cross-functional agreement from IT operations, development, and security

Core Concepts

SLA Framework Components
  1. Severity Classification: CVSS base score + threat context (EPSS, KEV)
  2. Asset Tiering: Business criticality and exposure level
  3. Remediation Timeframes: Maximum days to remediate by category
  4. Exception Process: Documented approval for SLA extensions
  5. Escalation Procedures: Actions when SLAs are breached
  6. Metrics and Reporting: KPIs for compliance tracking
SeverityTier 1 (Critical)Tier 2 (Important)Tier 3 (Standard)
Critical (CVSS 9.0-10.0)24-48 hours72 hours7 days
High (CVSS 7.0-8.9)7 days14 days30 days
Medium (CVSS 4.0-6.9)30 days45 days60 days
Low (CVSS 0.1-3.9)90 days90 days90 days
CISA KEV Listed24 hours48 hours7 days
SLA Accelerators (Reduce SLA by 50%)
  • Exploit code publicly available
  • Active exploitation observed in the wild (CISA KEV)
  • Internet-facing asset affected
  • EPSS score > 0.5 (50% exploitation probability)
  • Previous breach via similar vulnerability type

Workflow

Step 1: Define Asset Tiers
Tier 1 (Critical Assets):
- Customer-facing production systems
- Payment processing infrastructure
- Domain controllers and identity systems
- Core network infrastructure (firewalls, routers)
- Databases containing PII/PHI/PCI data

Tier 2 (Important Assets):
- Internal production applications
- Email and collaboration systems
- Development/staging environments with production data
- Backup and recovery infrastructure
- VPN and remote access gateways

Tier 3 (Standard Assets):
- End-user workstations
- Development/test environments
- Print servers and peripheral management
- Non-critical internal tools
Step 2: Establish SLA Policy Document

Key sections to include:

  • Purpose and scope
  • Roles and responsibilities (RACI matrix)
  • Severity definitions and calculation method
  • Remediation timeframes by severity and asset tier
  • Exception request process and approval authority
  • Escalation procedures for SLA breaches
  • Metrics, reporting cadence, and governance
  • Policy review and update schedule
Step 3: Integrate with Ticketing System
python
# ServiceNow / Jira integration for automatic ticket creation
# See process.py for full implementation

# Key fields for remediation tickets:
# - Vulnerability ID (CVE/Plugin ID)
# - Affected host(s)
# - Severity (CVSS + contextual factors)
# - Asset tier
# - SLA deadline (calculated from discovery date)
# - Assignment group
# - Remediation instructions
# - Verification criteria
Step 4: Configure Escalation Chain
SLA Status          Action                          Notify
───────────────────────────────────────────────────────────
75% elapsed         Warning email                   Asset owner
100% elapsed        SLA breach notification          Manager + CISO
100% + 7 days       Executive escalation             VP/CTO
100% + 30 days      Risk acceptance required          CISO approval
100% + 90 days      Compensating controls mandatory   Board report
Step 5: Establish Exception Process

Valid exception reasons:

  • System cannot be patched without major downtime (scheduled maintenance window)
  • No vendor patch available (apply compensating controls)
  • Patch breaks critical functionality (require test results as evidence)
  • End-of-life system pending decommission (document risk acceptance)

Exception requirements:

  • Written justification with business impact
  • Compensating controls documented and implemented
  • Approved by asset owner AND security leadership
  • Maximum exception duration: 90 days (renewable with re-approval)
  • Tracked in vulnerability management platform
Show full SKILL.md (229 more words)Show less

Key Performance Indicators (KPIs)

Primary Metrics
KPIDefinitionTarget
SLA Compliance Rate% of vulns remediated within SLA>90%
Mean Time to Remediate (MTTR)Average days from discovery to fixCritical: <3d, High: <10d
Vulnerability BacklogOpen vulnerabilities past SLA<5% of total
Exception Rate% of findings with active exceptions<10%
Recurrence Rate% of vulns that reappear after remediation<5%
  • Month-over-month SLA compliance trend
  • MTTR trend by severity
  • Vulnerability density per asset (vulns/host)
  • Patch coverage rate (% of assets scanned and compliant)
  • Time to first response (acknowledgment of finding)

Best Practices

  1. Start with achievable SLAs and tighten over time as maturity improves
  2. Use automated ticketing to eliminate manual SLA tracking
  3. Provide remediation teams with clear fix instructions, not just CVE numbers
  4. Track SLA compliance at the team/department level for accountability
  5. Report SLA metrics to executive leadership monthly
  6. Include compensating controls as valid interim remediation
  7. Align SLAs with regulatory requirements (PCI DSS, HIPAA, SOX)
  8. Review and adjust SLAs annually based on threat landscape changes

Common Pitfalls

  • Setting unrealistic SLAs that teams cannot meet (creates SLA fatigue)
  • No executive enforcement of SLA breaches
  • Treating all assets equally without tiering
  • Not accounting for vulnerability context (EPSS, KEV) in SLA calculation
  • Missing exception management process (leads to untracked risk)
  • Measuring only compliance rate without analyzing root causes of breaches
  • prioritizing-vulnerabilities-with-cvss-scoring
  • implementing-patch-management-workflow
  • implementing-vulnerability-metrics-and-reporting
  • implementing-exception-management-process

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/implementing-vulnerability-remediation-sla of mukul975/Anthropic-Cybersecurity-Skills.

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

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Implementing Vulnerability Remediation Sla next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implementing Vulnerability Remediation Sla compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implementing Vulnerability Remediation Sla this skillmukul975/Anthropic-Cybersecurity-Skills34k—~1.9kAutomated safety check: PassApache-2.0
Pine BacktesterTradersPost/pinescript-agents1701 repos~3.9kAutomated safety check: PassNone
Analytics Strategyrampstackco/claude-skills945—~2.4kAutomated safety check: PassMIT
Onboarding Plannerbpinheiroms/dotfiles108—~5.4kAutomated safety check: PassNone
Replit Decksanqiufong/slides-from-anything1321 repos~2.9kAutomated safety check: PassApache-2.0
Building Streamlit Dashboardsiusztinpaul/designing-real-world-ai-agents-workshop512—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Pine Backtester

    TradersPost/pinescript-agents

    Implements comprehensive backtesting and performance metrics.

    170 GitHub starsUsed in 1 repo~3.9k tokens
    Business, Finance & HRAuto-check passed

  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    945 GitHub stars~2.4k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed

  • Onboarding Planner

    bpinheiroms/dotfiles

    Plan high-conversion mobile app onboarding flows from scratch.

    108 GitHub stars~5.4k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed

  • Replit Deck

    sanqiufong/slides-from-anything

    Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.

    132 GitHub starsUsed in 1 repo~2.9k tokens
    Business, Finance & HRAuto-check passed

  • Building Streamlit Dashboards

    iusztinpaul/designing-real-world-ai-agents-workshop

    Building dashboards in Streamlit. An agent skill from iusztinpaul/designing-real-world-ai-agents-workshop.

    512 GitHub stars~1.1k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed

  • Massing Bim

    ibuilder/massing

    Drive a Massing BIM/AEC project from an AI agent over MCP — read a project's status, records, CDE, KPI and model-quality checks; run standards-compliance, schedule-risk, embodied-carbon, permit-…

    122 GitHub stars~1.1k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo

  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Implementing Vulnerability Remediation Sla

What does Implementing Vulnerability Remediation Sla do?

Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation…. Implementing Vulnerability Remediation Sla is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation KPIs/trending metrics.

When should I use Implementing Vulnerability Remediation Sla?

Implementing Vulnerability Remediation Sla fits situations like: defining mandatory patching timeframes by severity and asset criticality; building an SLA policy document; setting up escalation and KPI tracking for vulnerability remediation.

How do I install Implementing Vulnerability Remediation Sla in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-vulnerability-remediation-sla -a claude-code`. Or copy the skill folder (skills/implementing-vulnerability-remediation-sla in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-vulnerability-remediation-sla in your project. Claude Code loads it when a task matches its description.

How do I install Implementing Vulnerability Remediation Sla in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-vulnerability-remediation-sla -a codex`. Or copy the skill folder (skills/implementing-vulnerability-remediation-sla in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-vulnerability-remediation-sla in your project. Codex loads it when a task matches its description.

Can I use Implementing Vulnerability Remediation Sla in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-vulnerability-remediation-sla -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-vulnerability-remediation-sla, .gemini/skills/implementing-vulnerability-remediation-sla, .github/skills/implementing-vulnerability-remediation-sla and .opencode/skills/implementing-vulnerability-remediation-sla in your project.

What does Implementing Vulnerability Remediation Sla need to run?

Going by SKILL.md and its folder, Implementing Vulnerability Remediation Sla needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Implementing Vulnerability Remediation Sla access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Implementing Vulnerability Remediation Sla safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Implementing Vulnerability Remediation Sla use?

Implementing Vulnerability Remediation Sla is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implementing Vulnerability Remediation Sla use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Implementing Vulnerability Remediation Sla?

Skills that share tags, products or a category with Implementing Vulnerability Remediation Sla: Pine Backtester (TradersPost/pinescript-agents, 170 stars), Analytics Strategy (rampstackco/claude-skills, 945 stars), Onboarding Planner (bpinheiroms/dotfiles, 108 stars) and Replit Deck (sanqiufong/slides-from-anything, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implementing Vulnerability Remediation Sla?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.