Windows Security 4661 Detects Privileged AD User/Group SID Enumeration via SAM

Identifies SAM_USER/SAM_GROUP access events (4661) aimed at privileged SIDs or names containing 'admin' while ignoring computer accounts.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Samir Bousseaden (SigmaHQ), DRL 1.1
Published
2019-04-03
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 Windows Security events (EventID 4661) involving SAM_USER or SAM_GROUP objects whose names match common privileged account patterns (e.g., containing "admin" or ending with well-known privileged RID suffixes). Attackers often enumerate privileged users and groups to plan escalation and lateral movement, so monitoring these object access attempts helps surface early reconnaissance. It relies on Security log telemetry including ObjectType, ObjectName, EventID, and SubjectUserName for filtering out machine accounts.

Related detections9 linkedT1087.002 — drag to rearrange
Suspicious Active Directory Reconnaissance via ADExplorer or ADRecon (via process_creation)
Suspicious Service Principal Name Enumeration via Setspn by UAT-8837
Malicious Active Directory Enumeration via SharpHound or BloodHound (via process_creation)
Suspicious Group Discovery - Command (via process_creation)
SharpHound Host Enumeration Over Kerberos (via security)
SPN Enumeration Previous to Kerberoasting Attack - Native Commands (via process_creation)
Suspicious Active Directory Enumeration via AD Explorer Snapshot Process Creation
Malicious Account Added to Domain Admins Group via net Command
Suspicious Remote Connection to ADWS Port 9389 via security
Windows Security 4661 Detects Privileged AD User/Group SID Enumeration via SAM
Pivot detection · T1087.002 · 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.