Policy Expert

Windows NT Lan Manager Hardening Best Practices

Reading time: 4 Minutes Read
Ben Balkin
Updated on: September 17, 2025
Windows NT Lan Manager Hardening Best Practices

Windows LAN Manager (LM) and NTLM are legacy authentication protocols with significant security risks. In this article, we explain what NT Land Manager is, describe its major weaknesses, and best practices for hardening its security.

What You Will Learn

  • What is LAN Manager
  • How this technology is used
  • The risks of using LM and NTLMv1
  • How to configure the LAN Manager Authentication
  • Best LAN Manager Security Practices

What is Windows LAN Manager

Windows NT LAN Manager (NTLM) is an outdated challenge-response authentication protocol developed by Microsoft. Despite being surpassed by Kerberos, the NTLM authentication protocol remains in use as a form of Single Sign-On (SSO), allowing users to authenticate to applications without directly providing their passwords.

Depending on the version of NTLM, the protocol employs one of two one-way functions: NT LanMan and NTLM version 1 utilize the DES-based LanMan one-way function (LMOWF), whereas NTLMv2 utilizes the NT MD4-based one-way function (NTOWF).

Windows New Technology LAN Manager Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016

Present Implementations and Uses

NTLM authentication remains supported and is necessary for Windows authentication within systems set up as part of a workgroup. Additionally, NTLM authentication is employed for local logon authentication on non-domain controllers. While Kerberos version 5 authentication is the preferred method within Active Directory environments, NTLM may still be utilized by non-Microsoft or Microsoft applications.

Implementers should note that NTLM lacks support for modern cryptographic methods like AES or SHA-256. Instead, it relies on cyclic redundancy checks (CRC) or MD5 for integrity, and RC4 for encryption.

The process of deriving a key from a password follows the specifications outlined in RFC1320 and FIPS46-2. Hence, it is generally recommended that applications avoid using NTLM.

Decreasing NTLM protocol usage in an IT environment demands understanding both the deployed application requirements reliant on NTLM and the strategies and steps essential for configuring computing environments to adopt alternative protocols.

How to plan and manage a hardening project. Read our exclusive guide to get ahead

Learn More

Vulnerabilities in Windows NT LAN Manager

MITRE ATT&CK framework includes techniques that specifically target the NTLM (NT LAN Manager) authentication protocol. Several techniques that can be used to exploit vulnerabilities in NTLM are present in the MITRE ATT&CK framework, including:

  • T1208 – Kerberoasting
  • T1558 – Pass the Hash
  • T1552 – Pass the Ticket
  • T1110 – Brute Force
  • T1003 – Credential Dumping
  • T1559 – Replication Through Removable Media
  • T1204 – User Execution

Such techniques can be used to gain NTLM credentials and use them to obtain unauthorized access to a system or network. Organizations should consider using more secure authentication protocols, such as Kerberos, and implement best practices for securing NTLM, such as using NTLMv2 and implementing network-level controls to prevent NTLM relay attacks.

Insider’s Guide to Legacy Protocols Learn how to manage and eliminate outdated authentication risks.

Download the Guide

Hardening Windows New Technology LAN Manager

Configuration hardening can help to mitigate the risks associated with this legacy protocol.One important aspect of configuration hardening is disabling LM authentication. This can be done by modifying the registry settings on Windows systems or using Group Policy Objects (GPOs) to enforce the change across the entire network. By disabling LM authentication, an attacker would not be able to crack the LM hash of a user’s password and gain unauthorized access to the network.

Additionally, implementing strong password policies, regular password rotation, and regular monitoring of logs and network activities hardens the security of your network.

Overall, configuration hardening reduces the attack surface and prevents unauthorized access. When choosing an automated method, it will require you to use a ‘Hardening Automation Tool’ that will save you the need to perform lab testing, and save you time and money.

Follow these best practices to protect against cyber threats and the risks associated with legacy authentication protocols such as LAN Manager (LM).

Key Takeaways

  • LAN Manager authentication is outdated and insecure
  • NTLMv1 should be disabled
  • NTLMv2 and Kerberos are the secure alternatives
  • Configuring the LAN Manager Authentication Level policy is essential
  • Following these best practices protects against cyber threats

How CalCom Can Help

Server hardening is typically a challenging and time-consuming process, requiring significant investments of time and resources. CHS by CalCom offers a solution to this problem by automating the entire server hardening process. CHS can learn your network and eliminate the need for lab testing while ensuring that your production environment experiences no outages. This allows you to apply your policy directly to your production servers without any hassle.

FAQs

What is LAN Manager (LM) authentication?
LAN Manager (LM) is an outdated Windows authentication protocol that uses weak hashing, making it vulnerable to brute-force and replay attacks.
Why is NTLMv1 insecure compared to NTLMv2 or Kerberos?
NTLMv1 relies on weak cryptography and fixed-length challenges, exposing systems to credential theft, while NTLMv2 and Kerberos provide stronger encryption and verification.
What does the LAN Manager Authentication Level policy do?
This Windows security policy controls which authentication protocols are allowed, helping administrators enforce NTLMv2 or Kerberos while blocking LM and NTLMv1.
What are the risks of leaving LM or NTLMv1 enabled?
Enabling legacy authentication exposes environments to password cracking, pass-the-hash, and non-compliance with modern security standards.
How can CalCom CHS help with authentication hardening?
CalCom Hardening Solution (CHS) automates configuration management, enforces secure LAN Manager Authentication Level policies, and ensures compliance with Microsoft security best practices.
Ben Balkin
Ben Balkin is a professional writer and blogger specializing in technology and innovation. As a contributor to the Calcom blog, Ben shares practical insights, useful tips, and engaging articles designed to simplify complex processes and make advanced technological solutions accessible to everyone. His writing style is clear, insightful, and inspiring, reflecting his strong belief in technology's power to enhance quality of life and empower businesses.

Related Articles

About Us

Established in 2001, CalCom is the leading provider of server hardening solutions that help organizations address the rapidly changing security landscape, threats, and regulations. CalCom Hardening Suite (CHS) is a security baseline hardening solution that eliminates outages, reduces operational costs, and ensures a resilient, constantly hardened, and monitored server environment.

More about us
Background Shape
About Us

Stay Ahead with Our Newsletter

Get the latest insights, security tips, and exclusive resources straight to your inbox every month.

    Ready to simplify compliance?

    See automated compliance in action—book your demo today!