Windows Registry: SilentProcessExit lsass.exe Monitor Registration for Credential Dumping

Alerts on registry registrations for SilentProcessExit monitoring of lsass.exe, a potential precursor to credential dumping.

FreeReviewedSigma · Critical · v1
Product
windows
Category
registry_event
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-02-26
Updated
2026-07-30

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies registry changes that register a monitor for silent process exit of lsass.exe under the SilentProcessExit key path. Attackers can use this technique to trigger actions on lsass.exe termination that may support memory dumping and credential access. It relies on Windows registry event telemetry matching TargetObject paths containing Microsoft\Windows NT\CurrentVersion\SilentProcessExit\lsass.exe.

Related detections9 linkedT1003.001 — drag to rearrange
Malicious Mimikatz Credential Dumping via Command Line Arguments
Malicious Credential Extraction via Volatility Memory Analysis (via process_creation)
Suspicious Physical Memory Acquisition via WinPmem (via process_creation)
Malicious LSASS Credential Dump via Rundll32 Comsvcs MiniDump via Process Creation (via process_creation)
Suspicious LSASS Credential Access via PowerShell (via process_creation)
Suspicious LSASS Memory Dump via Task Manager After Ivanti Exploitation
Suspicious ProcDump LSASS Memory Dump via process_creation
Malicious Mimikatz Credential Dump Log File Creation (via file_event)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Windows Registry: SilentProcessExit lsass.exe Monitor Registration for Credential Dumping
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.