huntrule

Windows Registry: Disable CrashDump via CrashControl DWORD value

Alerts on registry changes that disable Windows crash dumps by writing 0x00000000 to CrashControl.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
Tobias Michalski (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-02-24
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Persistence → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows registry modifications that disable CrashDump by setting a DWORD value (0x00000000) under SYSTEM\CurrentControlSet\Control\CrashControl. Disabling crash dumps can reduce available forensic artifacts and impair incident response after malicious activity. The detection relies on registry-set telemetry that records the TargetObject path and the changed Details value.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Windows Registry: Disable CrashDump via CrashControl DWORD value
Pivot detection · T1112 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.