Windows LDAP Client Event ID 30 Active Directory enumeration via LDAP search filters

Flags LDAP search queries indicative of Active Directory reconnaissance/enumeration using Event ID 30 filter patterns.

FreeReviewedSigma · Medium · v2
Product
windows
Service
ldap
Author
Adeem Mawani (SigmaHQ), DRL 1.1
Published
2021-06-22
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 LDAP client activity that uses LDAP search filters associated with querying Active Directory objects and relationships. Such reconnaissance and enumeration can help attackers map users, groups, privileged accounts, and policy-related objects before follow-on access. It relies on Microsoft-Windows-LDAP-Client/Debug ETW telemetry (Event ID 30), matching specific LDAP SearchFilter patterns and DistinguishedName content indicative of directory discovery.

Related detections9 linkedT1069.002 — drag to rearrange
Windows File Events: ADExplorer .dat Snapshot Written by ADExp.exe or ADExplorer.exe
Windows: Sysinternals ADExplorer invoked with snapshot flag to create AD database snapshot
Windows Process Creation: Sysinternals ADExplorer Snapshot Exports Active Directory Database
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: Renamed AdFind.exe Executions
Windows file creation for SharpHound/BloodHound collection output filenames
Windows Process Creation: AdFind Executed with Suspicious Recon Flags
Windows Process Execution of Bloodhound/SharpHound Command-Line Collection Options
Windows LDAP Client Event ID 30 Active Directory enumeration via LDAP search filters
Pivot detection · T1069.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.