Windows LSASS Memory Access via Process Access Flags From Suspicious Paths

Alerts on processes attempting sensitive access to lsass.exe originating from suspicious/temp directories, using granted access and source path context.

FreeReviewedSigma · Medium · v7
Product
windows
Category
process_access
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-11-27
Updated
2026-09-15

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 flags process access to LSASS (lsass.exe) when the access rights granted include values commonly associated with credential dumping or memory inspection. It is significant because malware and post-exploitation tools often obtain LSASS memory by opening a handle with specific permissions. The detection relies on process access telemetry that includes the target process path, the granted access mask, and the source process image path containing common suspicious directories.

Related detections9 linkedT1003.001 — drag to rearrange
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)
Suspicious LSASS Memory Dump via Procdump Process Creation
Windows LSASS Memory Access via Process Access Flags From Suspicious Paths
Pivot detection · T1003.001 · 9 related

Changelog

v7
  1. v7
    Candidate ingested via manual entry.2026-09-15
  2. v5
    Candidate ingested via manual entry.2026-07-31
  3. v4
    Candidate ingested via manual entry.2026-07-31
  4. v3
    Candidate ingested via manual entry.2026-07-31
  5. v2
    Candidate ingested via manual entry.2026-07-31
  6. 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.