Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How should security teams plan a migration from…
Governance, Ownership & Risk

How should security teams plan a migration from NTLM to Kerberos in Windows environments?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Governance, Ownership & Risk

Start by inventorying where NTLM is still required, especially legacy applications, standalone systems, and backward compatibility paths. Then validate Kerberos support in Active Directory for critical services, test authentication flows, and phase out NTLM through Group Policy on the least impacted systems first. This reduces disruption while shifting the environment toward stronger mutual authentication and ticket-based access.

Where Kerberos migration work usually starts

The practical starting point is not Group Policy, it is dependency mapping. Security teams need to know which applications, services, devices, and administrative workflows still rely on NTLM so they can separate true blockers from legacy habits. That inventory becomes the basis for phased testing, exception handling, and business sequencing.

A useful way to frame the work is to treat NTLM as a compatibility dependency, not as a single toggle. In mixed Windows estates, the biggest migration mistakes are usually hidden dependencies, especially in older line-of-business systems, scheduled tasks, service-to-service connections, and cross-domain or trust-related paths that were never designed for modern Kerberos behavior.

For teams building that inventory, NTLM Deprecation and Elimination Guide is the most direct planning reference because it focuses on dependency mapping, phased blocking, and the operational shape of NTLM removal. If the migration is tied to broader directory cleanup, Active Directory and Entra ID Hardening Guide helps place the auth change inside a wider hardening programme rather than treating it as an isolated protocol swap.

How to validate Kerberos before you reduce NTLM

Kerberos migration succeeds when the directory, service identities, and application flows are all ready for it. That means validating SPNs, service account design, delegation requirements, time synchronisation, and any legacy behavior that depends on NTLM fallback. Teams should test the exact authentication paths used in production, not just a lab login scenario.

Pay particular attention to systems that are technically Kerberos-capable but operationally brittle, such as apps that break when tickets expire, services that depend on ambiguous name resolution, or workloads that silently fail over to NTLM when a configuration issue appears. The goal is to prove that the environment can authenticate consistently under normal load and during failure conditions before NTLM is restricted.

Where service identities are part of the migration path, the Windows Services and Service Account Security Guide is useful because service account design often determines whether Kerberos works cleanly. For server-side hardening work that commonly accompanies protocol migration, Windows Server Hardening Guide is a good companion reference for the underlying Windows controls that support stable Kerberos operation.

How to phase out NTLM without breaking production

The safest cutover pattern is staged reduction, not immediate removal. Start with the least critical systems, enable logging and monitoring first, and then constrain NTLM in small policy steps so you can observe what fails and why. This gives you a clean way to distinguish genuine application dependencies from transient misconfiguration.

Group Policy changes should follow the migration sequence, not lead it. Teams should first confirm that replacement Kerberos paths work for the selected systems, then restrict NTLM only where the failure impact is known and acceptable. If an application still requires NTLM, keep the exception narrow, time-bound, and owned by a named team rather than leaving it as an open-ended compatibility allowance.

For teams that need a broader migration pattern, Windows Endpoint Hardening Guide is useful because Kerberos migration often sits alongside other endpoint protections, such as credential theft reduction and baseline hardening. If you need a more complete cutover discipline for Windows estates, Windows Event Log Guide supports the monitoring side of the rollout, which is essential when you are watching for residual NTLM usage and authentication failures.

Risk and Threat Considerations

NTLM reduction changes the attack surface as well as the compatibility profile. The main risk is not just service disruption, it is leaving high-value exceptions in place long after the migration begins, which gives attackers a narrower but still usable authentication path. That is especially relevant where legacy services, shared credentials, or administrative workflows still depend on NTLM.

Failure mechanism: An incomplete migration leaves fallback paths, exception lists, or misconfigured services that continue to accept weaker authentication, allowing persistence, lateral movement, or reuse of exposed credentials.

Impact: Attackers may retain a practical path into systems that the organisation believes have already been modernised, which undermines the value of the Kerberos migration and prolongs exposure to password-hash-based abuse and downgrade opportunities.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Kerberos migration changes how Windows users authenticate to services.
IA-5 — Authenticator ManagementMigration depends on handling credentials, tickets, and fallback auth safely.
AU-2 — Event LoggingNTLM-to-Kerberos cutover needs log coverage to find remaining NTLM use.
Recommendation — Validate Kerberos user authentication paths before reducing NTLM. Rotate or retire credentials and tickets tied to NTLM-only dependencies. Enable logging that distinguishes NTLM from Kerberos authentication.
CIS Controls v8CIS-5 — Account ManagementAccount and service identity cleanup is central to Kerberos cutover.
CIS-8 — Audit Log ManagementThe plan depends on observing residual NTLM authentication during rollout.
Recommendation — Review and remove stale accounts or services that still require NTLM. Collect and review authentication logs throughout the phased migration.

Practitioner Guidance

What to verify: Do not trust a migration plan until you can show which applications still negotiate NTLM, which services have been tested under Kerberos-only conditions, and which exceptions are deliberately retained. The important evidence is not a project status deck, it is a confirmed list of residual dependencies and a tested rollback path.

Implementation sequence: Start with inventory and authentication telemetry, move to controlled testing of critical services, then phase policy enforcement by business criticality. The sequencing matters because NTLM removal is usually a dependency-management exercise first and a policy exercise second.

Practitioner takeaway: The right migration strategy is to prove Kerberos works before constraining NTLM, then reduce NTLM in small, observable steps so the remaining exceptions are intentional, bounded, and easy to retire.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org