Windows DNS Query for _ldap.* Using LDAP-Related Discovery

Alerts on _ldap.* DNS queries from uncommon Windows processes, indicating potential LDAP/DNS service discovery.

FreeReviewedSigma · Low · v2
Product
windows
Category
dns_query
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-08-20
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 DNS queries with a QueryName starting with "_ldap." that are generated by processes outside common baselines. Attackers may use LDAP-related discovery patterns that involve resolving service records via DNS to locate directory services or related infrastructure. The detection relies on DNS query telemetry and process image path context, excluding known benign system and browser/agent images and allowing visibility into unknown or uncommon callers.

Related detections9 linkedT1482 — drag to rearrange
Suspicious Discovery Command Spawned by Java Process
Uncommon Domain Trust Discovery via Nltest (via process_creation)
Suspicious SOAPHound Tautological LDAP Filter Enumeration
Suspicious Domain Trust Enumeration via Nltest
Suspicious Domain Controller and Trust Enumeration via Nltest
Suspicious Domain Trust Discovery via Nltest
Suspicious Active Directory Forest PowerShell Class Called from a Non Administrative Host (via powershell)
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 DNS Query for _ldap.* Using LDAP-Related Discovery
Pivot detection · T1482 · 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.