TL;DR: Pass-the-hash still gives attackers a replayable route inside Active Directory because NTLM can reuse cached hashes without cracking passwords, according to IS Decisions. Access controls and monitoring now decide how far a compromised identity can move after sign-in.
Editorial analysis by NHI Mgmt Group, based on content published by IS Decisions: “Pass-the-Hash attacks explained”.
Key questions
Q: Why does pass-the-hash increase lateral movement risk so much?
A: Because it lets an attacker reuse a valid internal credential instead of hunting for a new one at every step.
Q: How can security teams know whether NTLM is still actually needed?
A: They should inventory applications, devices, and service accounts that still generate NTLM traffic, then test whether Kerberos, local KDC, or IAKerb can replace that dependency.
Q: What breaks when NTLM is still enabled in Active Directory?
A: NTLM preserves a replayable trust path that attackers can abuse once they obtain cached hash material from a compromised endpoint.
Practitioner guidance
- Inventory NTLM dependencies Map every application, server, and fallback path still using NTLM so you can see where pass-the-hash remains viable.
- Restrict administrative workstation use Block admins from using Remote Desktop or other privileged logins on endpoints that are not trusted, patched, and tightly monitored.
- Pair MFA with session controls Use MFA as a foothold-reduction control, then add concurrent session limits, contextual access rules, and prompt restrictions to limit what happens after authentication.
Bottom line: NTLM still creates a practical attack path because reusable hashes can be replayed inside the protocol even when the password is never recovered.
Glossary terms: Pass-the-Hash, NTLMv1, Lateral Movement, Privilege Creep
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Pass-the-hash survives because NTLM treats a reusable hash as a valid trust artefact. That design was acceptable when the protocol was expected to be replaced, but it becomes a governance liability when the protocol lingers in production. The practical implication is that identity teams must treat NTLM presence as an active trust decision, not a legacy leftover.
A question worth separating out:
Q: How should teams limit damage when MFA does not stop protocol replay?
A: Treat MFA as one layer, not the control that ends the risk. Add contextual access restrictions, session limits, and endpoint hardening so a replayed hash cannot be used broadly after sign-in. The objective is to shrink what the authenticated account can reach if the protocol is abused.
👉 Read our full editorial: NTLM pass-the-hash shows why Active Directory controls still matter