patch-prioritization

Prioritize vulnerability remediation patches using SSVC 2.1, EPSS v3, and CISA KEV.

44|128|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/UnitOneAI/SecuritySkills --skill patch-prioritization-unitoneai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch-prioritization
Source: https://github.com/UnitOneAI/SecuritySkills/tree/main/skills/vuln-management/patch-prioritization
Command: npx skills add https://github.com/UnitOneAI/SecuritySkills --skill patch-prioritization-unitoneai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patch scheduling and SLA assignment often become inconsistent, slow, or disconnected from real exploitation risk, causing missed deadlines and unmanaged residual risk.

Core Features & Use Cases

  • SSVC 2.1-driven SLA tiering: Assigns remediation urgency using SSVC decision outcomes, with EPSS and CISA KEV used for validation and escalation.
  • EPSS v3 trend analysis: Detects surging and rising exploitation likelihood over 7/30/90-day windows to adjust patch urgency.
  • CISA KEV cross-referencing: Flags KEV-listed CVEs to enforce accelerated remediation expectations.
  • Compensating control and exception management: Evaluates whether interim mitigations justify SLA extensions and produces risk acceptance/exception artifacts with review/expiration controls.
  • Patch window scheduling support: Groups changes and aligns remediation actions to maintenance windows and change management constraints.

Quick Start

Prioritize and schedule remediation for your vulnerability backlog using SSVC 2.1, EPSS v3 trend analysis, and CISA KEV by running the patch-prioritization skill on the provided target list.

Frequently Asked Questions about patch-prioritization

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

FAQPage Schema
How do I prioritize vulnerability patches using SSVC and CISA KEV?

Patch prioritization assigns remediation SLAs using SSVC 2.1 decision outcomes while cross-referencing CISA KEV to accelerate remediation for actively exploited vulnerabilities. This approach aligns urgency with real exploitation risk rather than static severity ratings.

What is EPSS trend analysis and how does it affect patch scheduling?

EPSS v3 trend analysis detects surging and rising exploitation likelihood over 7, 30, and 90-day windows to dynamically adjust patch urgency. It helps prevent missed deadlines by escalating remediation priorities for vulnerabilities with increasing exploitation probability.

How do I manage risk acceptance and SLA extensions for known vulnerabilities?

Risk acceptance and SLA extensions are managed by evaluating whether compensating controls justify deadline adjustments for known vulnerabilities. This process generates exception artifacts with defined review and expiration controls to maintain unmanaged residual risk visibility.

Can I align vulnerability remediation with maintenance windows and change management?

Vulnerability remediation can be grouped and aligned with maintenance windows and change management constraints. This ensures patch window scheduling supports structured deployment while producing an audit-ready patch plan with dashboard metrics.

What data is required to generate an audit-ready patch plan with SLA tiers?

Generating an audit-ready patch plan requires collecting vulnerability inventory, asset criticality, exposure context, patch availability, and SLA deadlines. These inputs enable SSVC-driven SLA tiering and prevent prompt-injection-based SLA manipulation.