Microsoft Takes Major Security Step by Disabling NTLM Authentication by Default
Microsoft has announced plans to enhance Windows security by phasing out the NTLM (New Technology LAN Manager) authentication protocol. This change will affect future Windows releases, where NTLM will be disabled by default and replaced with more secure…
Microsoft has announced plans to enhance Windows security by phasing out the NTLM (New Technology LAN Manager) authentication protocol. This change will affect future Windows releases, where NTLM will be disabled by default and replaced with more secure Kerberos-based alternatives.
NTLM, a long-standing authentication protocol, is known for using challenge-response verification to access network resources. However, its outdated design presents significant security vulnerabilities, such as susceptibility to replay, man-in-the-middle, and pass-the-hash attacks. Despite being deprecated, NTLM remains in use due to dependencies in legacy systems and network constraints.
Microsoft is implementing a three-phase transition plan to ensure a smooth migration to more secure authentication methods:
Phase 1: Enhanced Visibility (Available Now)
Deploy enhanced NTLM auditing tools with Windows Server 2025 and Windows 11 version 24H2 and later. Identify where and why NTLM is in use within IT environments.
Microsoft has announced plans to enhance Windows security by phasing out the NTLM (New Technology LAN Manager) authentication protocol.
Phase 2: Reducing NTLM Dependencies (Second Half of 2026)
Introduce features such as IAKerb and local Key Distribution Center (KDC) technology. Enable Kerberos authentication without direct domain controller access. Support local account authentication without NTLM fallback.
Phase 3: NTLM Disabled by Default (Next Major Windows Release)
Network NTLM will be blocked by default, requiring administrative policy changes to re-enable. The system will default to Kerberos authentication while supporting legacy scenarios.
Microsoft advises immediate action to deploy enhanced NTLM auditing and identify dependencies. Organizations should prioritize remediation efforts, test NTLM-disabled configurations in non-production environments, and collaborate with application developers to migrate systems to Kerberos.
This transition is a critical step toward a more secure authentication environment aligned with Microsoft's goal of a passwordless future.
Based on reporting by GBHackers.
