Windows WSASS Process Execution via WerFaultSecure.EXE

Alerts on Windows process creation showing wsass.exe running with WerFaultSecure.exe and a PID-like argument.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-11-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 identifies execution of wsass.exe on Windows when its command line uses WerFaultSecure.exe, along with a PID argument. Attackers use this technique to facilitate LSASS memory dumping by leveraging Windows Error Reporting components to interact with protected processes. The detection relies on Windows process creation telemetry, including the executed image filename, an imphash match, and a command-line pattern that ties wsass.exe to werfaultsecure.exe and a numeric PID.

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 WSASS Process Execution via WerFaultSecure.EXE
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.