Kerberos relay is the reuse of a valid Kerberos ticket against a different service endpoint that accepts it without sufficient binding to the original channel or target. It is a service-level failure mode, not a password theft problem, and it becomes practical when signing or channel binding is missing.
How Kerberos relay works
Kerberos relay happens when an attacker reuses a valid Kerberos ticket against a different service endpoint that will accept it without enough binding to the original channel or target. The core problem is not ticket theft, but a service that cannot strongly distinguish the intended presentation context from a replayed one. That makes trust in the ticket alone insufficient.
In practice, relay is a protocol- and service-behaviour issue. If a service accepts a Kerberos-authenticated request without channel binding, signing, or other context checks, the ticket can be forwarded to another endpoint that honours it. The ticket may be valid, but the security assumption behind where it can be used has failed.
Why Kerberos relay is dangerous
Kerberos is designed to prove that an authenticated party can present a valid ticket, not to guarantee that every downstream service will correctly bind that ticket to the original transport or target. When that binding is weak or absent, the attacker can turn one legitimate authentication event into access against a different service than the one the user or system intended.
The danger is amplified in environments where services rely on Kerberos for single sign-on, delegation, or administrative access. A successful relay can bypass the normal friction of password capture, because the attacker does not need to crack a credential or manufacture a fake ticket. The weakness is acceptance logic at the service boundary.
Where organisations should look for exposure
Exposure usually sits in the services that accept Kerberos authentication and in the controls around them. The first check is simple asset inventory: identify which hosts, applications, and middleware components still accept Kerberos, then confirm whether they require signing, channel binding, or equivalent protections. Services exposed on networks where an attacker can position themselves between client and server are especially worth scrutiny.
Vendor advisories and hardening guidance matter here because relay resistance is often implementation-specific. For broader visibility into identity and access hardening expectations, see NIST SP 800-53 Rev 5 Security and Privacy Controls for control families that cover authentication, system integrity, and configuration management. For network and trust-boundary design, NIST SP 800-207 Zero Trust Architecture is a useful companion when thinking about service-to-service trust assumptions.
For Windows and mixed enterprise estates, the Kerberos Security Guide helps readers place relay alongside related Kerberos abuse patterns such as ticket replay, delegation issues, and detection priorities. That matters because relay risk is often missed when teams look only for stolen passwords or obvious ticket forgery.
Detection and response considerations
Detection is rarely about a single signature. Instead, teams should look for authentication flows that do not match expected source, destination, or protocol behaviour, especially where a service suddenly accepts Kerberos traffic in a pattern that differs from normal client-to-service paths. If the service should require stronger binding, any successful authentication through an unexpected relay path is itself a warning sign.
After remediation, review whether any service accepted a relayed ticket before the fix landed. If relay was possible, treat the event as a possible authentication boundary bypass and check for anomalous service use, privilege-sensitive actions, and lateral movement that followed the original authentication.
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, NIST Zero Trust (SP 800-207) and CIS Controls v8 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) | Kerberos relay exploits how services accept authenticated users. |
| IA-5 — Authenticator Management | Kerberos relay is a service-level authentication failure involving ticket use. | |
| IA-9 — Service Identification and Authentication | Kerberos relay targets service-to-service acceptance of valid authentication material. | |
| Recommendation — Require service authentication flows to bind accepted tickets to the intended user context and transport. Manage ticket handling and validation so reused Kerberos credentials cannot be accepted out of context. Enforce mutual service authentication and context binding for Kerberos-protected endpoints. | ||
| NIST Zero Trust (SP 800-207) | ZT-07 — (null) | Zero Trust emphasizes explicit verification at each service boundary. |
| Recommendation — Treat each Kerberos-enabled service as an independently verified trust decision. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Relay abuse succeeds when services accept access without sufficient binding. |
| Recommendation — Restrict service access paths so relayed authentication cannot cross intended boundaries. | ||
Practitioner Guidance
Why practitioners should care: Kerberos relay is a configuration and protocol-boundary problem, so the right response is to harden the service’s acceptance conditions rather than assume the ticket system is “secure by default.” Teams should verify where signing, channel binding, and related protections are actually enforced, not just documented.
What to watch for: Pay special attention to services that authenticate successfully even when they are reached through unexpected paths, proxying, or relaying opportunities. Those are the places where a valid ticket can become an unintended access path.
Practitioner takeaway: If a Kerberos-enabled service can be reached and accepted outside its intended trust context, the authentication design is incomplete even when ticket validation itself succeeds.
Related resources from NHI Mgmt Group
- Why do mixed NTLM and Kerberos environments create more relay exposure?
- What are the signs that an Active Directory environment is not protected against relay and Kerberos abuse?
- How do you detect Kerberos relay attacks such as KrbRelayUp on Windows?
- How should security teams reduce NTLM relay risk in Active Directory?
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 October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org