rootpwn

Threat Intel

LDAP Ping Detection: Why Event 1644 Falls Short and How to Spot It

Attackers use LDAP ping for lateral movement, but Windows Event 1644 logs miss this activity. Defenders can still detect LDAP ping through netlogon.log and other audit sources. Implement targeted monitoring to close the blind spot.

What Happened

Recent analysis shows that LDAP ping traffic, a common lateral movement technique, is not captured by Windows Security Event 1644 logs. Attackers exploit this gap to move through an environment without triggering the expected audit trail.

Why Event 1644 Misses It

Event 1644 records authentication attempts that succeed or fail, but LDAP ping is a lightweight, stateless request that does not result in a full authentication transaction. Consequently, the event generator does not emit a record for this traffic.

How Defenders Can Detect LDAP Ping

Netlogon.log and other system logs still record the underlying RPC and DNS queries associated with LDAP ping. By correlating these entries with unusual account activity or unexpected domain controller communication, defenders can surface the hidden movement.

What to Do

  • Enable and retain netlogon.log on all domain controllers.
  • Configure SIEM to parse netlogon.log for LDAP ping patterns (e.g., repeated SRV queries).
  • Set alerts for anomalous LDAP traffic volumes or unfamiliar source IPs.
  • Apply least‑privilege controls to service accounts that perform LDAP queries.

ldap netlogon event1644 audit defense monitoring

← All news