RPC Firewall detects remote DCOM/WMI-related RPC operations via specified interface UUIDs

Alerts on RPC Firewall RPC events indicating remote DCOM/WMI interface activity that can support lateral movement.

FreeReviewedSigma · High · v5
Product
rpc_firewall
Category
application
Author
Sagie Dulce, Dekel Paz (SigmaHQ), DRL 1.1
Published
2022-01-01
Updated
2026-07-31

ATT&CK techniques

Execution → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies RPC Firewall events where remote RPC calls perform operations associated with DCOM/WMI, based on matching specific Interface UUID values. Such traffic can be used to establish remote procedure execution paths that support lateral movement between hosts. Detection relies on RPC Firewall application telemetry (EventLog: RPCFW, EventID: 3) that records the interface UUID involved in the remote call.

Related detections9 linkedT1047 — drag to rearrange
Malicious UAT-8302 Remote Process Execution via wmic
Malicious Remote Encryptor Execution via WMIC Process Call Create (Chaos Ransomware)
Malicious Impacket Wmiexec Remote Command Execution Pattern
Malicious Shadow Copy Deletion Via WMI
Suspicious Remote Process Creation via WMIC Process Call Create (via process_creation)
Suspicious System Reconnaissance via WMI Command-Line Queries (via process_creation)
Malicious Impacket DCOMexec Process Abuse via MMC (via process_creation)
Malicious Impacket WMIexec Process Execution (via process_creation)
Suspicious Child Process Spawned by WMI Provider Host (via process_creation)
RPC Firewall detects remote DCOM/WMI-related RPC operations via specified interface UUIDs
Pivot detection · T1047 · 9 related

Changelog

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