[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73EE00HYYW1PJ29A5AXA0SW":3,"skill-same:01M73EE00HYYW1PJ29A5AXA0SW":114},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M73EE00HYYW1PJ29A5AXA0SW","performing-cve-prioritization-with-kev-catalog",null,"Leverage the CISA Known Exploited Vulnerabilities catalog alongside EPSS and CVSS to prioritize CVE remediation based on real-world exploitation evidence.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: performing-cve-prioritization-with-kev-catalog\ndescription: Leverage the CISA Known Exploited Vulnerabilities catalog alongside EPSS\n  and CVSS to prioritize CVE remediation based on real-world exploitation evidence.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- cisa-kev\n- cve\n- vulnerability-prioritization\n- epss\n- bod-22-01\n- threat-intelligence\n- remediation\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n# Performing CVE Prioritization with KEV Catalog\n\n## Overview\nThe CISA Known Exploited Vulnerabilities (KEV) catalog, established through Binding Operational Directive (BOD) 22-01, is a living list of CVEs that have been actively exploited in the wild and carry significant risk. As of early 2026, the catalog contains over 1,484 entries, growing 20% in 2025 alone with 245 new additions. This skill covers integrating the KEV catalog into vulnerability prioritization workflows alongside EPSS (Exploit Prediction Scoring System) and CVSS to create a risk-based approach that prioritizes vulnerabilities with confirmed exploitation activity over theoretical severity alone.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing cve prioritization with kev catalog\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Access to vulnerability scan results (Qualys, Nessus, Rapid7, etc.)\n- Familiarity with CVE identifiers and NVD\n- Understanding of CVSS scoring (v3.1 and v4.0)\n- API access to CISA KEV, EPSS, and NVD endpoints\n- Python 3.8+ with requests and pandas libraries\n\n## Core Concepts\n\n### CISA KEV Catalog Structure\nEach KEV entry contains:\n- **CVE ID**: The CVE identifier (e.g., CVE-2024-3094)\n- **Vendor\u002FProject**: Affected vendor and product name\n- **Vulnerability Name**: Short description of the vulnerability\n- **Date Added**: When CISA added it to the catalog\n- **Short Description**: Brief technical description\n- **Required Action**: Recommended remediation action\n- **Due Date**: Deadline for federal agencies (FCEB) to remediate\n- **Known Ransomware Campaign Use**: Whether ransomware groups exploit it\n\n### BOD 22-01 Remediation Timelines\n| CVE Publication Date | Remediation Deadline |\n|----------------------|---------------------|\n| 2021 or later | 2 weeks from KEV listing |\n| Before 2021 | 6 months from KEV listing |\n\n### Multi-Factor Prioritization Model\n\n| Factor | Weight | Data Source | Rationale |\n|--------|--------|-------------|-----------|\n| CISA KEV Listed | 30% | CISA KEV JSON feed | Confirmed active exploitation |\n| EPSS Score | 25% | FIRST EPSS API | Predicted exploitation probability |\n| CVSS Base Score | 20% | NVD API v2.0 | Intrinsic vulnerability severity |\n| Asset Criticality | 15% | CMDB\u002FAsset inventory | Business impact context |\n| Network Exposure | 10% | Network architecture | Attack surface accessibility |\n\n### KEV + EPSS Decision Matrix\n\n| KEV Listed | EPSS > 0.5 | CVSS >= 9.0 | Priority | SLA |\n|------------|-----------|-------------|----------|-----|\n| Yes | Any | Any | P1-Emergency | 48 hours |\n| No | Yes | Yes | P1-Emergency | 48 hours |\n| No | Yes | No | P2-Critical | 7 days |\n| No | No | Yes | P2-Critical | 7 days |\n| No | No | No (>= 7.0) | P3-High | 14 days |\n| No | No | No (>= 4.0) | P4-Medium | 30 days |\n| No | No | No (\u003C 4.0) | P5-Low | 90 days |\n\n## Workflow\n\n### Step 1: Fetch and Parse the KEV Catalog\n\n```python\nimport requests\nimport json\nfrom datetime import datetime\n\nKEV_URL = \"https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002Ffeeds\u002Fknown_exploited_vulnerabilities.json\"\n\ndef fetch_kev_catalog():\n    \"\"\"Download and parse the CISA KEV catalog.\"\"\"\n    response = requests.get(KEV_URL, timeout=30)\n    response.raise_for_status()\n    data = response.json()\n\n    catalog = {}\n    for vuln in data.get(\"vulnerabilities\", []):\n        cve_id = vuln[\"cveID\"]\n        catalog[cve_id] = {\n            \"vendor\": vuln.get(\"vendorProject\", \"\"),\n            \"product\": vuln.get(\"product\", \"\"),\n            \"name\": vuln.get(\"vulnerabilityName\", \"\"),\n            \"date_added\": vuln.get(\"dateAdded\", \"\"),\n            \"description\": vuln.get(\"shortDescription\", \"\"),\n            \"action\": vuln.get(\"requiredAction\", \"\"),\n            \"due_date\": vuln.get(\"dueDate\", \"\"),\n            \"ransomware_use\": vuln.get(\"knownRansomwareCampaignUse\", \"Unknown\"),\n        }\n\n    print(f\"[+] Loaded {len(catalog)} CVEs from CISA KEV catalog\")\n    print(f\"    Catalog version: {data.get('catalogVersion', 'N\u002FA')}\")\n    print(f\"    Last updated: {data.get('dateReleased', 'N\u002FA')}\")\n    return catalog\n\nkev = fetch_kev_catalog()\n```\n\n### Step 2: Enrich with EPSS Scores\n\n```python\nEPSS_API = \"https:\u002F\u002Fapi.first.org\u002Fdata\u002Fv1\u002Fepss\"\n\ndef get_epss_scores(cve_list):\n    \"\"\"Fetch EPSS scores for a batch of CVEs.\"\"\"\n    scores = {}\n    batch_size = 100\n    for i in range(0, len(cve_list), batch_size):\n        batch = cve_list[i:i + batch_size]\n        cve_param = \",\".join(batch)\n        response = requests.get(EPSS_API, params={\"cve\": cve_param}, timeout=30)\n        if response.status_code == 200:\n            for entry in response.json().get(\"data\", []):\n                scores[entry[\"cve\"]] = {\n                    \"epss\": float(entry.get(\"epss\", 0)),\n                    \"percentile\": float(entry.get(\"percentile\", 0)),\n                }\n    return scores\n```\n\n### Step 3: Build the Prioritization Engine\n\n```python\nimport pandas as pd\n\ndef prioritize_vulnerabilities(scan_results, kev_catalog, epss_scores):\n    \"\"\"Apply multi-factor prioritization to scan results.\"\"\"\n    prioritized = []\n\n    for vuln in scan_results:\n        cve_id = vuln.get(\"cve_id\", \"\")\n        cvss_score = float(vuln.get(\"cvss_score\", 0))\n        asset_criticality = float(vuln.get(\"asset_criticality\", 3))\n        exposure = float(vuln.get(\"network_exposure\", 3))\n\n        in_kev = cve_id in kev_catalog\n        kev_data = kev_catalog.get(cve_id, {})\n        epss_data = epss_scores.get(cve_id, {\"epss\": 0, \"percentile\": 0})\n        epss_score = epss_data[\"epss\"]\n\n        # Composite risk score calculation\n        risk_score = (\n            (1.0 if in_kev else 0.0) * 10 * 0.30 +\n            epss_score * 10 * 0.25 +\n            cvss_score * 0.20 +\n            (asset_criticality \u002F 5.0) * 10 * 0.15 +\n            (exposure \u002F 5.0) * 10 * 0.10\n        )\n\n        # Assign priority level\n        if in_kev or (epss_score > 0.5 and cvss_score >= 9.0):\n            priority = \"P1-Emergency\"\n            sla_days = 2\n        elif epss_score > 0.5 or cvss_score >= 9.0:\n            priority = \"P2-Critical\"\n            sla_days = 7\n        elif cvss_score >= 7.0:\n            priority = \"P3-High\"\n            sla_days = 14\n        elif cvss_score >= 4.0:\n            priority = \"P4-Medium\"\n            sla_days = 30\n        else:\n            priority = \"P5-Low\"\n            sla_days = 90\n\n        prioritized.append({\n            \"cve_id\": cve_id,\n            \"cvss_score\": cvss_score,\n            \"epss_score\": round(epss_score, 4),\n            \"epss_percentile\": round(epss_data[\"percentile\"], 4),\n            \"in_cisa_kev\": in_kev,\n            \"ransomware_use\": kev_data.get(\"ransomware_use\", \"N\u002FA\"),\n            \"kev_due_date\": kev_data.get(\"due_date\", \"N\u002FA\"),\n            \"risk_score\": round(risk_score, 2),\n            \"priority\": priority,\n            \"sla_days\": sla_days,\n            \"asset\": vuln.get(\"asset\", \"\"),\n            \"asset_criticality\": asset_criticality,\n        })\n\n    df = pd.DataFrame(prioritized)\n    df = df.sort_values(\"risk_score\", ascending=False)\n    return df\n```\n\n### Step 4: Generate Prioritization Report\n\n```python\ndef generate_report(df, output_file=\"kev_prioritized_report.csv\"):\n    \"\"\"Generate summary report from prioritized vulnerabilities.\"\"\"\n    print(\"\\n\" + \"=\" * 70)\n    print(\"VULNERABILITY PRIORITIZATION REPORT - KEV + EPSS + CVSS\")\n    print(\"=\" * 70)\n\n    print(f\"\\nTotal vulnerabilities analyzed: {len(df)}\")\n    print(f\"KEV-listed vulnerabilities:    {df['in_cisa_kev'].sum()}\")\n    print(f\"Ransomware-associated:         {(df['ransomware_use'] == 'Known').sum()}\")\n\n    print(\"\\nPriority Distribution:\")\n    print(df[\"priority\"].value_counts().to_string())\n\n    print(\"\\nTop 15 Highest Risk Vulnerabilities:\")\n    top = df.head(15)[[\"cve_id\", \"cvss_score\", \"epss_score\", \"in_cisa_kev\",\n                        \"risk_score\", \"priority\"]]\n    print(top.to_string(index=False))\n\n    df.to_csv(output_file, index=False)\n    print(f\"\\n[+] Full report saved to: {output_file}\")\n```\n\n## Best Practices\n1. Update the KEV catalog daily since CISA adds new entries multiple times per week\n2. Always cross-reference KEV with EPSS; a CVE may have high EPSS but not yet be in KEV\n3. Treat all KEV-listed CVEs as P1-Emergency regardless of CVSS score\n4. Pay special attention to KEV entries flagged with \"Known Ransomware Campaign Use\"\n5. Automate KEV comparison against your vulnerability scan results in CI\u002FCD pipelines\n6. Track KEV due dates separately for FCEB compliance requirements\n7. Use KEV as a leading indicator for threat hunting; if a CVE is added, check for prior exploitation in your environment\n\n## Common Pitfalls\n- Relying solely on CVSS scores without checking KEV or EPSS data\n- Not updating the KEV catalog frequently enough (CISA updates multiple times weekly)\n- Treating non-KEV CVEs as safe; they may be exploited but not yet cataloged\n- Ignoring the \"ransomware use\" field which indicates highest-urgency threats\n- Using KEV only for compliance instead of integrating into overall risk management\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- building-vulnerability-data-pipeline-with-api\n- implementing-threat-intelligence-scoring\n- implementing-vulnerability-remediation-sla\n","# Performing CVE Prioritization with KEV Catalog\n\n## Overview\nThe CISA Known Exploited Vulnerabilities (KEV) catalog, established through Binding Operational Directive (BOD) 22-01, is a living list of CVEs that have been actively exploited in the wild and carry significant risk. As of early 2026, the catalog contains over 1,484 entries, growing 20% in 2025 alone with 245 new additions. This skill covers integrating the KEV catalog into vulnerability prioritization workflows alongside EPSS (Exploit Prediction Scoring System) and CVSS to create a risk-based approach that prioritizes vulnerabilities with confirmed exploitation activity over theoretical severity alone.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing cve prioritization with kev catalog\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Access to vulnerability scan results (Qualys, Nessus, Rapid7, etc.)\n- Familiarity with CVE identifiers and NVD\n- Understanding of CVSS scoring (v3.1 and v4.0)\n- API access to CISA KEV, EPSS, and NVD endpoints\n- Python 3.8+ with requests and pandas libraries\n\n## Core Concepts\n\n### CISA KEV Catalog Structure\nEach KEV entry contains:\n- **CVE ID**: The CVE identifier (e.g., CVE-2024-3094)\n- **Vendor\u002FProject**: Affected vendor and product name\n- **Vulnerability Name**: Short description of the vulnerability\n- **Date Added**: When CISA added it to the catalog\n- **Short Description**: Brief technical description\n- **Required Action**: Recommended remediation action\n- **Due Date**: Deadline for federal agencies (FCEB) to remediate\n- **Known Ransomware Campaign Use**: Whether ransomware groups exploit it\n\n### BOD 22-01 Remediation Timelines\n| CVE Publication Date | Remediation Deadline |\n|----------------------|---------------------|\n| 2021 or later | 2 weeks from KEV listing |\n| Before 2021 | 6 months from KEV listing |\n\n### Multi-Factor Prioritization Model\n\n| Factor | Weight | Data Source | Rationale |\n|--------|--------|-------------|-----------|\n| CISA KEV Listed | 30% | CISA KEV JSON feed | Confirmed active exploitation |\n| EPSS Score | 25% | FIRST EPSS API | Predicted exploitation probability |\n| CVSS Base Score | 20% | NVD API v2.0 | Intrinsic vulnerability severity |\n| Asset Criticality | 15% | CMDB\u002FAsset inventory | Business impact context |\n| Network Exposure | 10% | Network architecture | Attack surface accessibility |\n\n### KEV + EPSS Decision Matrix\n\n| KEV Listed | EPSS > 0.5 | CVSS >= 9.0 | Priority | SLA |\n|------------|-----------|-------------|----------|-----|\n| Yes | Any | Any | P1-Emergency | 48 hours |\n| No | Yes | Yes | P1-Emergency | 48 hours |\n| No | Yes | No | P2-Critical | 7 days |\n| No | No | Yes | P2-Critical | 7 days |\n| No | No | No (>= 7.0) | P3-High | 14 days |\n| No | No | No (>= 4.0) | P4-Medium | 30 days |\n| No | No | No (\u003C 4.0) | P5-Low | 90 days |\n\n## Workflow\n\n### Step 1: Fetch and Parse the KEV Catalog\n\n```python\nimport requests\nimport json\nfrom datetime import datetime\n\nKEV_URL = \"https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002Ffeeds\u002Fknown_exploited_vulnerabilities.json\"\n\ndef fetch_kev_catalog():\n    \"\"\"Download and parse the CISA KEV catalog.\"\"\"\n    response = requests.get(KEV_URL, timeout=30)\n    response.raise_for_status()\n    data = response.json()\n\n    catalog = {}\n    for vuln in data.get(\"vulnerabilities\", []):\n        cve_id = vuln[\"cveID\"]\n        catalog[cve_id] = {\n            \"vendor\": vuln.get(\"vendorProject\", \"\"),\n            \"product\": vuln.get(\"product\", \"\"),\n            \"name\": vuln.get(\"vulnerabilityName\", \"\"),\n            \"date_added\": vuln.get(\"dateAdded\", \"\"),\n            \"description\": vuln.get(\"shortDescription\", \"\"),\n            \"action\": vuln.get(\"requiredAction\", \"\"),\n            \"due_date\": vuln.get(\"dueDate\", \"\"),\n            \"ransomware_use\": vuln.get(\"knownRansomwareCampaignUse\", \"Unknown\"),\n        }\n\n    print(f\"[+] Loaded {len(catalog)} CVEs from CISA KEV catalog\")\n    print(f\"    Catalog version: {data.get('catalogVersion', 'N\u002FA')}\")\n    print(f\"    Last updated: {data.get('dateReleased', 'N\u002FA')}\")\n    return catalog\n\nkev = fetch_kev_catalog()\n```\n\n### Step 2: Enrich with EPSS Scores\n\n```python\nEPSS_API = \"https:\u002F\u002Fapi.first.org\u002Fdata\u002Fv1\u002Fepss\"\n\ndef get_epss_scores(cve_list):\n    \"\"\"Fetch EPSS scores for a batch of CVEs.\"\"\"\n    scores = {}\n    batch_size = 100\n    for i in range(0, len(cve_list), batch_size):\n        batch = cve_list[i:i + batch_size]\n        cve_param = \",\".join(batch)\n        response = requests.get(EPSS_API, params={\"cve\": cve_param}, timeout=30)\n        if response.status_code == 200:\n            for entry in response.json().get(\"data\", []):\n                scores[entry[\"cve\"]] = {\n                    \"epss\": float(entry.get(\"epss\", 0)),\n                    \"percentile\": float(entry.get(\"percentile\", 0)),\n                }\n    return scores\n```\n\n### Step 3: Build the Prioritization Engine\n\n```python\nimport pandas as pd\n\ndef prioritize_vulnerabilities(scan_results, kev_catalog, epss_scores):\n    \"\"\"Apply multi-factor prioritization to scan results.\"\"\"\n    prioritized = []\n\n    for vuln in scan_results:\n        cve_id = vuln.get(\"cve_id\", \"\")\n        cvss_score = float(vuln.get(\"cvss_score\", 0))\n        asset_criticality = float(vuln.get(\"asset_criticality\", 3))\n        exposure = float(vuln.get(\"network_exposure\", 3))\n\n        in_kev = cve_id in kev_catalog\n        kev_data = kev_catalog.get(cve_id, {})\n        epss_data = epss_scores.get(cve_id, {\"epss\": 0, \"percentile\": 0})\n        epss_score = epss_data[\"epss\"]\n\n        # Composite risk score calculation\n        risk_score = (\n            (1.0 if in_kev else 0.0) * 10 * 0.30 +\n            epss_score * 10 * 0.25 +\n            cvss_score * 0.20 +\n            (asset_criticality \u002F 5.0) * 10 * 0.15 +\n            (exposure \u002F 5.0) * 10 * 0.10\n        )\n\n        # Assign priority level\n        if in_kev or (epss_score > 0.5 and cvss_score >= 9.0):\n            priority = \"P1-Emergency\"\n            sla_days = 2\n        elif epss_score > 0.5 or cvss_score >= 9.0:\n            priority = \"P2-Critical\"\n            sla_days = 7\n        elif cvss_score >= 7.0:\n            priority = \"P3-High\"\n            sla_days = 14\n        elif cvss_score >= 4.0:\n            priority = \"P4-Medium\"\n            sla_days = 30\n        else:\n            priority = \"P5-Low\"\n            sla_days = 90\n\n        prioritized.append({\n            \"cve_id\": cve_id,\n            \"cvss_score\": cvss_score,\n            \"epss_score\": round(epss_score, 4),\n            \"epss_percentile\": round(epss_data[\"percentile\"], 4),\n            \"in_cisa_kev\": in_kev,\n            \"ransomware_use\": kev_data.get(\"ransomware_use\", \"N\u002FA\"),\n            \"kev_due_date\": kev_data.get(\"due_date\", \"N\u002FA\"),\n            \"risk_score\": round(risk_score, 2),\n            \"priority\": priority,\n            \"sla_days\": sla_days,\n            \"asset\": vuln.get(\"asset\", \"\"),\n            \"asset_criticality\": asset_criticality,\n        })\n\n    df = pd.DataFrame(prioritized)\n    df = df.sort_values(\"risk_score\", ascending=False)\n    return df\n```\n\n### Step 4: Generate Prioritization Report\n\n```python\ndef generate_report(df, output_file=\"kev_prioritized_report.csv\"):\n    \"\"\"Generate summary report from prioritized vulnerabilities.\"\"\"\n    print(\"\\n\" + \"=\" * 70)\n    print(\"VULNERABILITY PRIORITIZATION REPORT - KEV + EPSS + CVSS\")\n    print(\"=\" * 70)\n\n    print(f\"\\nTotal vulnerabilities analyzed: {len(df)}\")\n    print(f\"KEV-listed vulnerabilities:    {df['in_cisa_kev'].sum()}\")\n    print(f\"Ransomware-associated:         {(df['ransomware_use'] == 'Known').sum()}\")\n\n    print(\"\\nPriority Distribution:\")\n    print(df[\"priority\"].value_counts().to_string())\n\n    print(\"\\nTop 15 Highest Risk Vulnerabilities:\")\n    top = df.head(15)[[\"cve_id\", \"cvss_score\", \"epss_score\", \"in_cisa_kev\",\n                        \"risk_score\", \"priority\"]]\n    print(top.to_string(index=False))\n\n    df.to_csv(output_file, index=False)\n    print(f\"\\n[+] Full report saved to: {output_file}\")\n```\n\n## Best Practices\n1. Update the KEV catalog daily since CISA adds new entries multiple times per week\n2. Always cross-reference KEV with EPSS; a CVE may have high EPSS but not yet be in KEV\n3. Treat all KEV-listed CVEs as P1-Emergency regardless of CVSS score\n4. Pay special attention to KEV entries flagged with \"Known Ransomware Campaign Use\"\n5. Automate KEV comparison against your vulnerability scan results in CI\u002FCD pipelines\n6. Track KEV due dates separately for FCEB compliance requirements\n7. Use KEV as a leading indicator for threat hunting; if a CVE is added, check for prior exploitation in your environment\n\n## Common Pitfalls\n- Relying solely on CVSS scores without checking KEV or EPSS data\n- Not updating the KEV catalog frequently enough (CISA updates multiple times weekly)\n- Treating non-KEV CVEs as safe; they may be exploited but not yet cataloged\n- Ignoring the \"ransomware use\" field which indicates highest-urgency threats\n- Using KEV only for compliance instead of integrating into overall risk management\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- building-vulnerability-data-pipeline-with-api\n- implementing-threat-intelligence-scoring\n- implementing-vulnerability-remediation-sla\n",{"name":5,"tags":25,"author":33,"domain":34,"source":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"nist_ai_rmf":43,"mitre_attack":47,"source_commit":51,"atlas_techniques":52},[26,27,28,29,30,31,32],"cisa-kev","cve","vulnerability-prioritization","epss","bod-22-01","threat-intelligence","remediation","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[38,39,40,41],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06","vulnerability-management",[44,45,46],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[48,49,50],"T1190","T1203","T1068","04450304b12645cb2b974ab96d28c0664758a88d",[53,54,55],"AML.T0070","AML.T0066","AML.T0082","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill performing-cve-prioritization-with-kev-catalog",{"tool":72,"command":73},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill performing-cve-prioritization-with-kev-catalog",{"tool":75,"command":76},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill performing-cve-prioritization-with-kev-catalog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002FSKILL.md",true,[80,86,90,96,100,104,110],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Ftemplate.md","ASSET","资产文件",1215,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002Fassets\u002Ftemplate.md",{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fapi-reference.md","REFERENCE","参考文档",5373,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002Freferences\u002Fapi-reference.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fstandards.md",1188,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002Freferences\u002Fstandards.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fworkflows.md",2865,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002Freferences\u002Fworkflows.md",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fagent.py","SCRIPT","脚本",8874,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002Fscripts\u002Fagent.py",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fprocess.py",9577,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cve-prioritization-with-kev-catalog\u002Fscripts\u002Fprocess.py",[115,123,130,138,146,154],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":119,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]