Teams should make relay paths unusable rather than merely harder to exploit. That means enforcing LDAP signing and channel binding, limiting where NTLM is accepted, and removing services that can be coerced into authenticating on behalf of an attacker. The goal is to prevent a captured session from being trusted anywhere else.
Why NTLM relay resistance in Active Directory depends on removing trust shortcuts
NTLM relay becomes viable when an attacker can capture or coerce authentication and then reuse it against a different service that still accepts the resulting session. The defensive target is not just blocking one tool or one path, but removing the assumptions that make relayed authentication acceptable anywhere in the domain.
That is why teams should focus on protocol hardening and trust boundaries together. A single control rarely solves relay by itself if another server, service, or legacy application still accepts unauthenticated or weakly protected binds.
To make that practical, harden the authentication surface, especially where Active Directory services accept directory binds or downstream application traffic. Where relayed authentication is still possible, the remaining weakness is usually a combination of legacy protocol acceptance, coercible services, and incomplete enforcement of signing or binding requirements.
Where relay risk usually persists in real Active Directory environments
Relay risk is rarely confined to one protocol setting. It usually persists where LDAP, SMB, or other Windows services accept credentials without the protections that stop an attacker from replaying them elsewhere, or where a host can be coerced into authenticating outward on the attacker’s terms.
That means the most important exposure is often not the initial capture of a session, but the presence of additional services that will trust that session after it has been relayed. If one service enforces protection and another does not, the weaker service becomes the practical attack target.
Internal hardening guidance on NTLM Relay Guide and the broader Lateral Movement Guide are useful here because relay is often part of a wider chain that includes coercion, name-resolution abuse, and post-authentication movement. The practical question is which pathways still accept relayed authentication, not whether one specific relay vector has been blocked.
How to verify you have actually reduced relay paths
The best verification is to test whether the environment still accepts relayed authentication at all, especially on directory services and any system that can be induced to authenticate to an untrusted listener. Do not rely only on configuration intent or group policy placement; confirm that the enforced setting is active on the servers that matter.
For AD teams, that usually means checking whether LDAP signing and channel binding are truly enforced, whether NTLM is still accepted where Kerberos should be preferred, and whether services that can be coerced into authenticating outward are still present. If a service can be made to initiate authentication on behalf of an attacker, treat it as part of the relay attack surface.
The LDAP Security Deep Dive Guide is a strong companion when you need to validate unsigned binds, channel binding enforcement, and application service bind hygiene. For broader dependency reduction, the NTLM Deprecation and Elimination Guide helps teams separate immediate relay blocking from the longer migration off NTLM.
Risk and Threat Considerations
NTLM relay is dangerous because it turns a captured or coerced authentication event into reusable access against another service that still trusts the relayed session. The risk is highest when legacy protocol acceptance, insufficient LDAP protection, or coercible services exist together, because each weak point expands the blast radius of one intercepted handshake.
Failure mechanism: An attacker captures or induces authentication, then relays it to a different service that does not require the protections needed to prove the session is bound to the original context.
Impact: The attacker can obtain unauthorized access, perform directory or service actions as the victim, and use that foothold to move laterally or escalate the compromise into broader domain access.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | NTLM relay exploits weak user authentication trust boundaries in AD. |
| IA-5 — Authenticator Management | Relay risk drops when credentials and authenticators are tightly managed and rotated. | |
| IA-9 — Identification and Authentication (Non-Organizational Users) | Services and systems that authenticate to each other need stronger machine-side authentication controls. | |
| Recommendation — Enforce stronger authentication for organizational users and reduce NTLM acceptance. Review authenticator lifecycle and remove long-lived or reusable credentials. Apply service-to-service authentication controls where NTLM is still used. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | NTLM relay is an access-path problem that requires tighter control of who can reach what. |
| CIS-8 — Audit Log Management | Validation of relay reduction depends on detecting coercion and relay attempts. | |
| Recommendation — Restrict access paths and remove unnecessary authentication acceptance points. Log and review authentication events that reveal NTLM relay activity. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity management, authentication and access enforcement | Relay prevention depends on enforcing authentication and access rules that block trusted reuse. |
| PR.DS-01 — Data-at-rest is protected | AD relay often targets protected directory data and credentials indirectly. | |
| Recommendation — Enforce authentication controls that prevent relayed sessions from being reused. Protect sensitive identity and directory data that relay attackers may target. | ||
| MITRE ATT&CK | T1557.001 — Adversary-in-the-Middle: LLMNR/NBT-NS Poisoning and SMB Relay | NTLM relay is a named adversary technique with established detection and hardening patterns. |
| Recommendation — Map detections and mitigations to SMB relay and related coercion techniques. | ||
Practitioner Guidance
What to prioritise: Start with the services that make relay profitable, not with the easiest hostname to harden. LDAP signing, channel binding, and NTLM restriction matter most where directory trust has the highest blast radius, especially on domain controllers and systems that other hosts authenticate to automatically.
What to verify: Confirm the control state on production systems, then test for residual relayable services and coercion paths. If a system still accepts NTLM where a stronger mechanism is available, or if it can be tricked into authenticating outward, treat that as an active exposure rather than a theoretical one.
Decision rule: If a service is operationally dependent on NTLM today, isolate it, document the dependency, and plan a migration path before you widen blocking. If the service is not business-critical, remove the acceptance path instead of preserving it for convenience.
Practitioner takeaway: Relay resistance is strongest when teams remove trust in the relayed session itself, not when they only add more logging around it.
Related resources from NHI Mgmt Group
- Guide: Active Directory and Entra ID Hardening Guide
- How should security teams reduce the risk of password guessing attacks in Active Directory?
- How should security teams reduce Kerberoasting risk in Active Directory?
- How should security teams reduce the risk of Golden Ticket attacks in Active Directory?
- How should security teams reduce Active Directory privilege risk?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org