RPC Firewall Logs: Remote Encryption Service RPC Call Detected for Lateral Movement

Alerts on RPC Firewall events indicating remote MS-EFSR encryption service RPC activity that may 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
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags an RPC Firewall event indicating a remote call to a specific interface UUID associated with the MS-EFSR remote encryption service. Such targeted remote service interaction can be abused to enable lateral movement by forcing actions through remote RPC endpoints. It relies on RPC Firewall application logs (EventLog "RPCFW") with EventID 3 and the matching InterfaceUuid value.

Related detections9 linkedT1569.002 — drag to rearrange
PsExec Remote Service Execution on Target Host (via process_creation)
Renamed Procdump Tool Used for Dumping LSASS Process (via process_creation)
Suspicious Service Installation Masquerading as winupd
Suspicious PSexec Application Execution (via process_creation)
Malicious Metasploit PsExec Named Pipe Command Execution
Malicious PsExec Service Installation via PSEXESVC
Malicious NotPetya Payload Execution via Rundll32 Ordinal Export from Windows Directory
Suspicious Lateral Movement via PsExec Service (via process_creation)
Possible PsExec Remote Service Installation with Randomly Named Service (via security)
RPC Firewall Logs: Remote Encryption Service RPC Call Detected for Lateral Movement
Pivot detection · T1569.002 · 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.