Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.
The Stakeholder-Specific Vulnerability Categorization (SSVC) framework, developed by Carnegie Mellon University's Software Engineering Institute (SEI) in collaboration with CISA, provides a structured decision-tree methodology for vulnerability prioritization. Unlike CVSS alone, SSVC accounts for exploitation status, technical impact, automatability, mission prevalence, and public well-being impact to produce one of four actionable outcomes: Track, Track*, Attend, or Act.
When to Use
When managing security operations that require triaging vulnerabilities with ssvc framework
When improving security program maturity and operational processes
When establishing standardized procedures for security team workflows
When integrating threat intelligence or vulnerability data into operations
Common Misconfigurations & Verification
Exploitation status from CVSS — verify Exploitation is driven by CISA KEV/EPSS evidence, not severity.
Automatability misjudged — verify AV:N/AC:L/UI:N maps to "yes" only with real worm/scriptability, not assumption.
Mission prevalence guessed — verify Essential/Support/Minimal comes from asset inventory, not a default.
Decision tree drift — verify outcomes against the reference cases in the validation tests (Act/Attend) after any logic change.
Outcome→SLA not enforced — verify Act=48h and Attend=14d actually drive ticketing deadlines.
Stale KEV feed — verify the catalog refreshes before triage so "Active" status is current.
Prerequisites
Python 3.9+ with requests, pandas, and jinja2 libraries
Access to CISA KEV catalog API and EPSS API from FIRST
NVD API key (optional, for higher rate limits)
Vulnerability scan results from tools like OpenVAS, Nessus, or Qualys
SSVC Decision Points
1. Exploitation Status
Assess current exploitation activity:
None - No evidence of active exploitation
PoC - Proof-of-concept exists publicly
Active - Active exploitation observed in the wild (check CISA KEV)
# Check if a CVE is in CISA Known Exploited Vulnerabilities catalog
curl -s | \
python3 -c
"import sys,json; data=json.load(sys.stdin); cves=[v['cveID'] for v in data['vulnerabilities']]; print('Active' if 'CVE-2024-3400' in cves else 'Check PoC/None')"
2. Technical Impact
Determine scope of compromise if exploited:
Partial - Limited to a subset of system functionality or data
Total - Full control of the affected system, complete data access
3. Automatability
Evaluate if exploitation can be automated at scale:
No - Requires manual, targeted exploitation per victim
Yes - Can be scripted or worm-like propagation is possible
4. Mission Prevalence
How widespread is the affected product in your environment:
Minimal - Limited deployment, non-critical systems
Support - Supports mission-critical functions indirectly