← ClaudeAtlas

verify-windows-mitigationslisted

Verification-and-drift methodology for confirming Windows exploit mitigations are enforced per host and per process, not merely named in policy: DEP, ASLR, CFG, CET shadow stack, SEHOP, heap integrity, ACG, Code Integrity Guard, and image-load and child-process blocking (MITRE ATT&CK T1203, T1190, T1068, T1211, T1210; mitigation M1050). Signals: Get-ProcessMitigation and NOTSET inheritance, MitigationOptions registry values, the Security-Mitigations event channels, Application log 1000 and 1001, and Defender for Endpoint DeviceEvents. Gives how to read live enforcement, find NOTSET and precedence gaps, detect baseline drift, hunt mitigations firing, and harden with a GPO or Intune baseline. Use when confirming exploit mitigations are enforced, verifying ASLR DEP CFG CET SEHOP coverage on a Windows fleet, auditing per-process mitigation state, reconciling an Exploit Protection XML baseline, or triaging a fast-fail crash cluster.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Verify Windows Exploit Mitigations Are Enforced - 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 A mitigation named in a policy document is not a mitigation that is enforced on the process in front of you. This skill is about closing that gap: proving which of DEP, ASLR (bottom-up and mandatory), CFG, CET shadow stack, SEHOP, heap-integrity, ACG, Code Integrity Guard, remote and low-integrity image blocking, and child-process blocking is live on each host and each running image, and finding where the answer is silently "none". The verification tool is `Get-ProcessMitigation`; the two traps are `NOTSET` (which means "inherit", not "on") and the rule that per-app Program settings override System settings. Build one Exploit Protection XML baseline, deploy it by GPO or Intune, and then treat any divergence between that XML and live `Get-ProcessMitigation` output as drift to investigate. The detection value is secondary: when a mitigation fires or a mitigated exploit fails, you see audit events in the Security-Mitigati