performing-cve-prioritization-with-kev-catalog

Prioritize CVE remediation using CISA KEV, EPSS, and CVSS scoring data.

1|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Yenn503/Net-Runners --skill performing-cve-prioritization-with-kev-catalog-yenn503
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performing-cve-prioritization-with-kev-catalog
Source: https://github.com/Yenn503/Net-Runners/tree/main/.netrunner/skills/reporting/performing-cve-prioritization-with-kev-catalog
Command: npx skills add https://github.com/Yenn503/Net-Runners --skill performing-cve-prioritization-with-kev-catalog-yenn503

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, pandas.

What problem does it solve? Security teams face thousands of CVEs from vulnerability scans and cannot patch everything at once. This Skill ranks vulnerabilities by real-world exploitation evidence instead of raw CVSS severity, so teams fix actively exploited flaws first. ## Core Features & Use Cases - KEV Catalog Integration: Fetches and parses the CISA Known Exploited Vulnerabilities JSON feed, including ransomware-use flags and BOD 22-01 due dates. - Multi-Factor Risk Scoring: Combines KEV listing (30%), EPSS probability (25%), CVSS base score (20%), asset criticality (15%), and network exposure (10%) into a composite risk score. - Priority Assignment with SLAs: Maps vulnerabilities to P1-Emergency through P5-Low tiers with remediation deadlines from 48 hours to 90 days. - Use Case: A security analyst exports Nessus scan results, runs the prioritization engine, and produces a CSV report showing which CVEs are KEV-listed, ransomware-associated, and require patching within 48 hours. ## Quick Start Ask the agent to fetch the CISA KEV catalog, enrich your vulnerability scan results with EPSS scores, and generate a prioritized remediation report sorted by risk score.

Frequently Asked Questions about performing-cve-prioritization-with-kev-catalog

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

FAQPage Schema
How do I prioritize CVEs using the CISA KEV catalog?▼

Fetch the KEV JSON feed from CISA, match your scan results against listed CVE IDs, and treat any match as P1-Emergency regardless of CVSS score. Combine this with EPSS scores and asset criticality for a weighted composite risk ranking.

What is the difference between CVSS, EPSS, and CISA KEV for vulnerability prioritization?▼

CVSS measures intrinsic severity, EPSS predicts the probability of future exploitation, and KEV confirms vulnerabilities already exploited in the wild. Using all three together prioritizes real-world risk over theoretical severity alone.

How often should I update the CISA KEV catalog data?▼

Update the KEV catalog daily because CISA adds new entries multiple times per week. Stale catalog data causes newly exploited vulnerabilities to be missed in prioritization runs.

What Python libraries are needed for KEV-based vulnerability prioritization?▼

The workflow requires Python 3.8 or later with the requests library for calling the CISA KEV and FIRST EPSS APIs, and pandas for building, sorting, and exporting the prioritized vulnerability DataFrame to CSV.

What are the limitations of relying only on the KEV catalog?▼

KEV only lists vulnerabilities with confirmed exploitation, so actively exploited but not-yet-cataloged CVEs are missed. Cross-reference with EPSS scores above 0.5 to catch high-probability threats before they enter the catalog.