← ClaudeAtlas

triage-vuln-classeslisted

Defensive triage methodology for classifying and prioritizing bug classes, the blue-team answer to offensive bug identification. Unremediated or mis-ranked vulnerabilities are what an adversary turns into Exploit Public-Facing Application (MITRE ATT&CK T1190) and the exploitation family (T1203, T1068, T1210, T1212, T1211), after recon and vuln sourcing (T1595.002, T1588.006). Works over your vulnerability data: scanner findings, SAST/DAST/SCA output (Semgrep, CodeQL, Trivy/Grype), and pentest reports, enriched with NVD CVSS v4.0, FIRST EPSS, the CISA KEV catalog, CWE, and CISA SSVC. Gives a classify-then-rank method that survives findings with no CVE, a hunt pivoting top classes to active-exploitation evidence, and remediation hardening mapped to ISO 27001 and NIST CSF 2.0. Use when triaging scanner or pentest findings, building a prioritization or SLA policy, deciding what to patch first, or reconciling CVSS against EPSS and KEV.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Discovered Bug Classes - Triage and Prioritization Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's classification and prioritization method, the data sources and signals, the hunt, and the hardening, and points to public, maintained rule sources by URL. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet. ## TL;DR for defenders Triage is a ranking discipline, not a scan. You already have more findings than you can fix; the job is to put them in the right order and defend that order. Classify every finding by its bug class (map it to a CWE and to the exploit primitive it grants, for example memory corruption to code execution, injection to data or command control, broken access control to privilege escalation), then rank by a combination of exploitability and exposure, not by vendor severity alone. The single most useful rule: a vulnerability that is in the **CISA KEV catalog** or has a high **EPSS** probability **and** sits on an internet-facing asset outranks a higher-CVSS bug that is internal-only and has no known exploit. Score CVE-bearing findings with CVSS v4.0, EPSS, and KEV; score first-party findings that have **no CVE** (authz flaws, business logic, SSRF in your own code) with CWE class severit