defend-exploit-mitigationslisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Exploit Mitigations (ASLR, DEP, CFG, CET) - 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, 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
Exploit mitigations are a hardening control first and a detection source second. ASLR, DEP/NX, CFG, and CET each remove a primitive an exploit depends on, so the highest-value work is coverage: knowing which mitigations are actually enforced on every process and every image, then closing the gaps where a binary ships without CFG or without a CETCOMPAT load-config. The detection value is secondary but real: when a mitigation fires or an exploit fails mid-run, the process crashes, and a cluster of fast-fail (`0xc0000409`) or access-violation (`0xc0000005`) crashes on an internet-facing service is a strong exploitation signal. Audit coverage with `Get-ProcessMitigation`, `dumpbin`, BinSkim, winchecksec, and `checksec`; watch the Security-Mitigations channels and Windows Error Reporting for the crashes; harden with the Essential Eight. No single mitigation is complete, so measure the set end to end.
## What it looks like, defen