SharpHound Account Recon via RPC Firewall Block (OpNum 2, Interface UUID)

Alerts on RPC Firewall EventID 3 with the Interface UUID and OpNum used by SharpHound for account discovery.

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 indicating SharpHound-issued remote procedure calls used for account discovery, specifically mapping remote connections and local group membership. The behavior is important because account discovery is a common early step in lateral movement and privilege targeting. It relies on RPC Firewall EventLog entries (EventID 3) that include InterfaceUuid 6bffd098-a112-3610-9833-46c3f87e345a and OpNum 2.

Related detections9 linkedT1087 — drag to rearrange
Suspicious Active Directory Discovery via ADFind
Suspicious Active Directory Enumeration via Sysinternals AD Explorer Snapshot (via process_creation)
Suspicious SimpleHelp Remote Access Client Spawning Discovery Commands (via process_creation)
Uncommon ADWS (Port 9389) Connections from Non-Standard Windows Binaries
Windows Process Creation: SOAPHound Execution via AD Data Collection Command-Line Arguments
Windows Process Creation Signals for Pikabot System Discovery
Windows PowerShell module commandlet names matching known exploitation and post-exploitation tooling
Windows Process Creation: Suspicious PowerShell Commandlets Used by Known Exploitation Tools
Windows Process Creation: Seatbelt.exe PUA Discovery Command-Line Execution
SharpHound Account Recon via RPC Firewall Block (OpNum 2, Interface UUID)
Pivot detection · T1087 · 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.