SharpHound RPC Firewall Recon: Remote Mapping and Group Membership Enumeration

Alerts on RPC Firewall EventID 3 for SharpHound-style discovery RPC calls to interface UUID with OpNum 12.

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

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags RPC Firewall events where SharpHound-related activity triggers a specific RPC interface UUID and operation number. Such RPC calls are used to enumerate and map remote connections and local group membership, which can support later lateral movement. It relies on RPC Firewall application telemetry (EventLog RPCFW, EventID 3) containing the targeted InterfaceUuid and OpNum values.

Related detections9 linkedT1033 — drag to rearrange
Suspicious Whoami Discovery Spawned by Windows Script Host via Process Creation (via process_creation)
Suspicious Localized Administrator Account and Group Enumeration After Citrix Bleed Exploitation
Malicious Recon Output Staged in Qlik Sense Fonts Directory by Cactus Ransomware
Suspicious Host Reconnaissance Command Chain via cmd
Malicious Child Process Spawned From n8n Node Process
Suspicious Credential Enumeration via cmdkey List
Suspicious IIS Worker Process Spawning Whoami Reconnaissance
Suspicious Whoami Execution With Output Redirected to a File (via process_creation)
Possible Logged-On Session Discovery via Quser or Qwinsta (via process_creation)
SharpHound RPC Firewall Recon: Remote Mapping and Group Membership Enumeration
Pivot detection · T1033 · 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.