Windows Security Log LSASS Access by Non-Computer Account Process

Alerts on suspicious LSASS access attempts (4663/4656) targeting lsass.exe by non-system processes using flagged access masks.

FreeReviewedSigma · Medium · v2
Product
windows
Service
security
Author
Roberto Rodriguez @Cyb3rWard0g (SigmaHQ), DRL 1.1
Published
2019-06-20
Updated
2026-07-31

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 Windows Security audit events (4663/4656) where a process attempts access to \lsass.exe using access masks consistent with credential-stealing tools. Attackers may target LSASS to extract credentials, making this behavior high risk even when the access is partial or indirect. It relies on process-object access telemetry and filters out common service/computer account patterns and likely benign process paths (e.g., Program Files software and WmiPrvSE-specific access).

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 Security Log LSASS Access by Non-Computer Account Process
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.