Windows: Suspicious LSASS handle access via svchost.exe call trace to seclogon.dll

Flags svchost.exe attempting LSASS access (granted access 0x14c0) with seclogon.dll in the call trace.

FreeReviewedSigma · High · v2
Product
windows
Category
process_access
Author
Samir Bousseaden (original elastic rule), Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-29
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

Identifies process access events where svchost.exe requests a specific granted access right to lsass.exe and the call trace includes seclogon.dll. Attackers may use this path to obtain a handle to LSASS in order to access credentials from memory. The rule relies on Windows process access telemetry that provides TargetImage, SourceImage, GrantedAccess, and CallTrace.

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: Suspicious LSASS handle access via svchost.exe call trace to seclogon.dll
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.