Join our Newsletter — 33% off our NHI Course
Home› Glossary› Authentication, Authorisation & Trust› NTLM Type 3 Message
Authentication, Authorisation & Trust

NTLM Type 3 Message

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Authentication, Authorisation & Trust

The NTLM Type 3 Message is the final authentication message a client sends in NTLM challenge-response authentication. It carries the username, domain, workstation name and the computed response to the server challenge, allowing the server to verify the client without sending the password itself.

How the NTLM Type 3 Message Works

The Type 3 message is the final client response in the NTLM challenge-response sequence. It packages the identity claim and the computed proof of knowledge that the server checks against its own expected value, so the password itself is never sent on the wire.

This is the message that turns the earlier challenge into an authentication result. In practical terms, it is the handoff point where the client proves it can answer the server’s nonce using the stored secret material associated with the account.

What the Type 3 Message Contains

A Type 3 message typically carries the username, domain, workstation name and the response value derived from the challenge. Those fields tell the server who is attempting to authenticate and from which context, while the response is what the server validates cryptographically.

The exact contents matter because NTLM is not a password exchange, it is a proof exchange. If an attacker can capture the Type 3 message, they may not learn the password directly, but they can still obtain material that can be replayed, relayed or used for offline verification attempts depending on the surrounding protocol conditions.

That is why hardening guidance for Active Directory and Entra ID Hardening Guide matters here, since NTLM usage sits inside wider Windows authentication and delegation choices.

Why It Is Security-Sensitive

The Type 3 message is security-sensitive because it is the place where a captured authentication exchange becomes useful to an attacker. If NTLM is accepted across weakly protected paths, the message can support pass-the-hash style abuse, relay attacks, or credential harvesting against systems that still trust NTLM.

Its risk is not that it reveals the cleartext password, but that it can still be leveraged when legacy authentication, poor channel protection, or excessive trust boundaries exist. The surrounding environment determines whether the message is merely an authentication artifact or a viable abuse primitive.

Attackers also care about the account context inside the message. Service accounts, privileged users and administrative workstations are especially valuable, which is why published breach analysis such as Cisco Active Directory credentials leak 2025 is relevant to the broader lesson: once authentication material is exposed, lateral movement opportunities often follow.

How Organisations Assess and Contain Exposure

Exposure assessment starts with finding where NTLM is still enabled, where it is negotiated by default, and where high-value systems still accept it. Asset inventory, authentication logs, endpoint policy review and server configuration checks are the practical ways to locate the systems that can emit or accept Type 3 messages.

Containment usually means reducing NTLM’s reach, tightening where it is permitted, and ensuring that the transport and endpoint controls around it are strong enough to resist interception or relay. If NTLM cannot yet be removed, the organisation should at least ensure that the systems handling it are treated as sensitive authentication boundaries.

Control mapping is typically anchored in identity and access hardening, secure authentication design and least-privilege architecture, with NIST SP 800-53 Rev 5 Security and Privacy Controls providing a direct control baseline for authentication and access management. For broader architecture choices, NIST Privacy Framework and NIST Cybersecurity Framework 2.0 are useful for governance and risk framing.

Detection, Response and Post-Use Review

Detection should focus on unusual NTLM authentication patterns, especially where a Type 3 exchange appears from an unexpected host, at an unusual time, or against a system that should not need NTLM at all. Correlating authentication events with lateral movement indicators often reveals whether the message was part of normal legacy compatibility or an active abuse chain.

After suspected abuse, teams should review the accounts that authenticated, the hosts that sent or accepted the message, and whether any cached or reusable credential material may have been exposed. That review should extend to service accounts, administrative sessions and any privileged access paths that could have been reached after the NTLM exchange.

Threat hunting and technique mapping benefit from MITRE ATT&CK Enterprise Matrix, especially for credential access and lateral movement patterns that commonly follow NTLM abuse.

Risk and Threat Considerations

NTLM Type 3 messages are risky because they turn a single captured authentication exchange into a potential path for replay, relay or privilege expansion when legacy trust remains in place. The exposure is highest where NTLM is still accepted broadly, where privileged accounts use it, or where network controls do not stop interception and reuse.

Failure mechanism: An attacker captures or relays the Type 3 exchange, then uses the trusted response or the account context it carries to authenticate elsewhere without ever learning the original password.

Impact: Compromise can escalate from one intercepted session to broader Windows domain access, especially if the authenticated account has excessive privilege or can reach sensitive internal systems.

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 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)Type 3 messages are part of organizational user authentication flows.
IA-5 — Authenticator ManagementNTLM depends on credential material that must be managed securely across its lifecycle.
AC-6 — Least PrivilegeNTLM abuse becomes more damaging when authenticated accounts have excessive rights.
Recommendation — Enforce strong user authentication and reduce reliance on legacy NTLM paths. Protect, rotate and retire authenticator material that underpins NTLM access. Limit account privilege so intercepted NTLM authentication has less blast radius.
CIS Controls v8CIS-6 — Access Control ManagementNTLM exposure is reduced when legacy authentication paths are constrained and reviewed.
Recommendation — Restrict legacy authentication paths and remove unnecessary access opportunities.
MITRE ATT&CKT1550 — Use Alternate Authentication MaterialCaptured NTLM responses can support alternate authentication abuse and lateral movement.
Recommendation — Map NTLM abuse to alternate authentication material techniques in detection content.

Practitioner Guidance

Why practitioners should care: NTLM Type 3 is often the last place a legacy authentication decision becomes visible, so it is a practical signal for where modern controls are still missing. Treat every system that emits or accepts it as part of the authentication attack surface, not just a compatibility detail.

What to watch for: Review where NTLM remains enabled, which accounts use it, and whether privileged or service identities are still dependent on it. If you see Type 3 traffic on sensitive segments or from endpoints that should be using stronger authentication, that is a remediation priority.

Practitioner takeaway: The safest long-term posture is to shrink NTLM’s footprint, not to rely on it as a default path for critical authentication.

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 November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org