CyberKit

Network ports

Port 636/tcp: LDAPS (LDAP over TLS/SSL)

Category: Name Resolution & Directory Services. Range: well-known. Status: iana registered.

What runs here

Port 636/tcp is LDAP wrapped in implicit TLS from connection start, the same directory query and modify functionality as 389, but encrypted before any LDAP operation occurs. It predates the standardized StartTLS extension (RFC 4513) and is not itself part of the core LDAP RFC series; it is a widely-deployed de facto convention that Microsoft and other directory vendors continue to support, and which Active Directory hardening guidance increasingly pushes as the default over unsigned plaintext LDAP.

Why it matters

It carries the same reconnaissance risk profile as 389, directory enumeration and privileged-group or attribute targeting, but with credentials and query content protected on the wire, so detection again relies on connection volume and source-host anomalies plus directory-side audit logging rather than packet inspection.

Where you see it

Legitimately: applications and clients configured to require encrypted directory access, especially after AD hardening that disables unsigned or unencrypted LDAP binds. Anomalously/maliciously: the same enumeration tooling used against 389, such as BloodHound or AdFind, simply configured to use LDAPS, or an attacker probing whether unauthenticated LDAPS binds are permitted.

What to look for

Indicators
SignalWhat it means
Directory-side object access auditingSince the wire content is encrypted, correlating LDAPS connection spikes with directory service access logs, such as Windows Security Event ID 4662, is the practical way to see what was actually queried.

Related ports

  • 389/tcp/udp: LDAP (Lightweight Directory Access Protocol)
  • 3269/tcp: Global Catalog LDAP over TLS/SSL

ATT&CK techniques

Sources