Windows PowerShell: Get-Process querying lsass within a ScriptBlock

Alerts when PowerShell ScriptBlock text runs Get-Process against lsass, a common credential-access precursor.

FreeReviewedSigma · High · v2
Product
windows
Category
ps_script
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-04-23
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 PowerShell ScriptBlock content containing the specific command to query the lsass process via Get-Process. Accessing or enumerating LSASS is a common prerequisite for credential theft and is often indicative of malicious post-compromise activity. It relies on ScriptBlock Logging telemetry capturing the ScriptBlock text of PowerShell execution.

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 PowerShell: Get-Process querying lsass within a ScriptBlock
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.