huntrule

Windows Registry: LSASS Full Dump via WER LocalDumps DumpType=2

Flags registry changes enabling LSASS full memory dumps by setting WER LocalDumps DumpType to 0x2.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
@pbssubhash (SigmaHQ), DRL 1.1
Published
2022-12-08
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Cred Access

  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 matches Windows registry updates where the DumpType value under Windows Error Reporting LocalDumps is set to a DWORD value of 0x00000002 (Full Dump) for the lsass.exe local dump configuration. Setting DumpType to 2 enables creation of full memory dumps of LSASS, which attackers can use to extract credentials from process memory. Detection relies on registry set telemetry capturing the TargetObject path and the Details value indicating a full dump setting.

Reporting behind it

Related detections9 linkedT1003.001 — drag to rearrange
Malicious WDigest Credential Caching Enabled via Registry (via registry_set)
Malicious Credential Dumping via Mimikatz Sekurlsa Command
Malicious Mimikatz Sekurlsa Logonpasswords Credential Dump
Malicious LSASS Credential Dump via ProcDump (via process_creation)
Malicious LSASS Memory Dump via comsvcs.dll by Salt Typhoon
Malicious LSASS Dump via Process Access (via process_access)
Malicious LSASS Credential Dump with LSASSY - Process (via process_creation)
Malicious LSASS Credential Dump with LSASSY - Admin Share (via security)
Malicious Task Manager Used for LSASS Dump - Kernel (via security)
Windows Registry: LSASS Full Dump via WER LocalDumps DumpType=2
Pivot detection · T1003.001 · 9 related

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