Quick answer
NTLM is Windows' older login protocol. It is behind pass-the-hash and NTLM relay attacks, and Microsoft is phasing it out in favor of Kerberos. Disabling it safely means auditing where it is still used, fixing or exempting those systems, then restricting it step by step, starting with domain controllers and privileged accounts.
On this page
Most Windows networks still use NTLM somewhere, usually without anyone knowing where. That leftover NTLM is what makes relay and pass-the-hash attacks work. Removing it is a long-term project, but each step shrinks the attack surface.
How It Works
The process runs in stages, each controlled through Group Policy under Security Options ("Network security: Restrict NTLM" settings) and the LAN Manager authentication level.
| Stage | What you do | Risk of breaking things |
|---|---|---|
| 1. Block NTLMv1 and LM | Set LAN Manager authentication level to send NTLMv2 only and refuse LM and NTLM | Low |
| 2. Audit | Turn on "Restrict NTLM: Audit" settings on domain controllers and servers, and collect the NTLM operational logs | None |
| 3. Fix dependencies | Use names instead of IP addresses, register service principal names, update or replace legacy applications | Varies |
| 4. Protect privileged accounts | Put administrators in Protected Users, which blocks NTLM for them | Low |
| 5. Restrict | Deny NTLM on domain controllers and high-value servers, with exceptions for anything that still needs it | Medium |
| 6. Remove | Deny NTLM domain-wide once the exception list is empty | Planned |
Why It Matters
Every relay attack in our internal tests and every pass-the-hash path depends on NTLM. Restricting it, alongside SMB signing and LDAP signing and channel binding, closes whole classes of attack rather than individual findings.
How to Test for It
- Check the LAN Manager authentication level and whether NTLMv1 is still accepted anywhere.
- Review NTLM audit logs to see which systems and accounts still use it.
- Check whether privileged accounts are in Protected Users.
- In an authorized test, attempt relay and pass-the-hash to confirm which paths remain.
How to Reduce the Risk
Work through the stages in order: block NTLMv1 now, audit for a few weeks, fix the top dependencies, protect privileged accounts, then restrict on domain controllers and critical servers before going domain-wide. Track exceptions with an owner and an end date so they shrink over time.
Regulatory and Framework Context
For US organizations, restricting legacy authentication appears in CIS Benchmarks for Windows and CISA and NSA Active Directory guidance, and supports NIST SP 800-53 identification and authentication controls. Our Active Directory security assessment shows which NTLM paths an attacker could use today.
Latest intel on this topic
- ⚡ Weekly Recap: N-able 0-Days, Windows 0-Days, Chrome 0-Days, Fridge 0-Days, and More Bad DaysThe Hacker News · November 16, 2026
- New SignDrop Zero-Day Exploit Turns Windows CLFS Security Feature Into SYSTEM AccessThe Hacker News · November 12, 2026
- Critical Zoom Workplace Flaw Could Allow Unauthenticated Remote Privilege EscalationThe Hacker News · November 11, 2026
- November Patch Tuesday: An Overflowing Cornucopia of CVEsDark Reading · November 10, 2026
- Microsoft Fixes Nearly 1,100 Security VulnerabilitiesKrebs on Security · November 10, 2026
Updated hourly from the daily briefing.
Common questions
Why is NTLM insecure?
NTLM does not prove which server you meant to log in to, so logins can be relayed, and its password hashes can be reused directly (pass-the-hash) or cracked offline. Kerberos and modern authentication avoid most of these weaknesses.
Can we just turn NTLM off?
Rarely in one step. Older applications, appliances, systems accessed by IP address instead of name, and some third-party tools still depend on it. Turning it off without auditing usually breaks something important.
What is NTLMv1 and should it go first?
NTLMv1 is the oldest and weakest version and can be cracked quickly. Blocking NTLMv1 (LAN Manager authentication level set to send NTLMv2 only and refuse LM and NTLM) is a safe early step in most networks.
Is Microsoft removing NTLM?
Microsoft has announced NTLM is deprecated and is adding Kerberos features to replace its remaining uses. Organizations that start auditing and restricting now will find the change far easier.
Change log
- November 14, 2026First published.