triage-crashes-defensivelylisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Crash Exploitability Triage - Defensive Methodology
> **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule sources. 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
Crash triage for a defender is two jobs, and everything below splits on which one you are doing. **Job A, prioritization:** rank crashes from your own fuzzing, CI, or sanitizer runs so you fix the memory-safety bugs that an attacker could realistically turn into code execution before the ones that only cause a clean abort. **Job B, exploitation signal:** read crash telemetry from production as evidence of an attempt, because the fuzzing an attacker does against your exposed service looks exactly like a cluster of access-violation crashes in one module. The highest-value rank signals are the low-volume, high-confidence ones: a Windows fail-fast (`0xc0000409`) or heap-corruption (`0xc0000374`) means a mitigation already caught a memory-safety bug, so it outranks the flood of ordinary `0xc0000005` access violations. On the sanitizer side, a WRITE outranks a READ, and a use-after-free or heap-overflow write outranks a near-null READ segfault. You do not nee