huntrule

Windows LSASS Memory Access Triggered by Source Image Containing 'dump' Keyword

Alerts when a process named with 'dump' requests specific access rights to lsass.exe on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
process_access
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-02-10
Updated
2026-07-31
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 identifies process access events where the target process is lsass.exe and the source process image name contains the keyword "dump". It also requires the granted access value to match a set of specific hexadecimal and numeric rights consistent with attempts to read or capture sensitive process memory. This matters because attackers may use tools with "dump" in the filename to obtain credential material from LSASS. The detection relies on Windows process access telemetry that records SourceImage, TargetImage, and GrantedAccess values.

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 LSASS Memory Access Triggered by Source Image Containing 'dump' Keyword
Pivot detection · T1003.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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