LDAP vs Kerberos vs Ntlm
When comparing ldap vs kerberos vs ntlm, LDAP reads user profiles while Kerberos and NTLM check user keys. Teams choose LDAP for directory lookups, Kerberos for modern ticket log in, and NTLM only for legacy fallback. Many engineers mix up these three tools because they often run together on Windows servers. Each protocol solves a distinct piece of the network identity puzzle. Knowing how they work helps you lock down internal systems. How ldap vs kerberos vs ntlm work in your stack LDAP sta
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
When comparing ldap vs kerberos vs ntlm, LDAP reads user profiles while Kerberos and NTLM check user keys. Teams choose LDAP for directory lookups, Kerberos for modern ticket log in, and NTLM only for legacy fallback.
Many engineers mix up these three tools because they often run together on Windows servers. Each protocol solves a distinct piece of the network identity puzzle. Knowing how they work helps you lock down internal systems.
How ldap vs kerberos vs ntlm work in your stack
LDAP stands for Lightweight Directory Access Protocol. It acts like a phone book for your network. Apps use LDAP to find user names, emails, and group roles. LDAP can also check a user password through a simple bind request. Still, plain LDAP sends data in clear text unless you wrap it in TLS.
Kerberos is a ticket protocol that checks identity without sending passwords over the wire. A central server called the Key Distribution Center gives the user a short-lived encrypted ticket. The user shows this ticket to network apps to log in fast. Kerberos checks both the user and the server to stop spoofing attacks. It is the default log in method for modern Active Directory domains.
NTLM is an older challenge and response protocol from Microsoft. The server sends a random number to the client machine. The client hashes the number with the user password hash and sends it back. NTLM does not verify the server identity to the client. Modern teams replace NTLM with Kerberos whenever an app supports tickets.
How LDAP and Kerberos work together
In most enterprise networks, you do not pick just one protocol. Active Directory uses Kerberos and LDAP side by side every day. A user logs into a laptop using Kerberos to prove who they are. Next, the app queries LDAP to read what groups that user belongs to.
Kerberos handles the log in step with strong math and encrypted tickets. LDAP handles the lookup step by reading attributes from the central tree. NTLM sits in the background only for old systems that cannot use Kerberos tickets. For example, logging into a server by raw IP address often triggers NTLM fallback.
LDAP Directory Services + K8s RBAC Role vs ClusterRole: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Security tradeoffs and modern runtime controls
Each protocol brings specific security risks that engineers must manage. NTLM is vulnerable to pass-the-hash and relay attacks on local networks. Attackers can capture an NTLM response and replay it to gain server access. Because of this risk, security teams work to turn off NTLM across their domains.
Kerberos is much safer, yet it requires strict clock sync across all machines. It also needs clean DNS records and Service Principal Names to issue tickets. If a ticket has a long lifespan, an attacker might steal it from memory. LDAP is safe for reading role data, but simple binds expose passwords if TLS fails.
These three protocols only check identity at the start of a network session. They cannot see what a user does inside a database or server after logging in. A user with a valid Kerberos ticket can still run a bad query. They might also pull sensitive rows full of customer emails or card numbers. Static directory groups rarely match the exact data a developer needs for a quick fix. Pairing directory log in with runtime controls lets teams check every command and mask sensitive fields like phone numbers or national IDs in results.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Can you use LDAP and Kerberos at the same time?
Yes, most Windows domains run both protocols together by default. Kerberos checks the user identity with a ticket, and LDAP reads their group roles.
Why should teams turn off NTLM?
NTLM uses older hashing math and does not check the server identity. Attackers can relay NTLM challenges to take over admin accounts on your network.
Does LDAP check passwords or just read user profiles?
LDAP does both jobs in many networks. It stores and reads user attributes, and it can verify passwords through a bind check over TLS.
Related guides
In this post