Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Golden Ticket

← Back to Glossary
By NHI Mgmt Group Updated November 19, 2026 Domain: Threats, Abuse & Incident Response

A Golden Ticket is a forged Kerberos ticket created from stolen domain-level cryptographic material. It gives the attacker durable access that can survive ordinary account resets, which makes it a persistence mechanism inside the identity layer.

What Golden Tickets Are, and Why They Matter

A Golden Ticket is not just a forged logon artifact, it is a Kerberos ticket built from domain-level cryptographic material that can let an attacker impersonate trusted access inside Active Directory. Because the ticket is minted from material at the identity trust layer, it can outlive ordinary password resets and behave like durable persistence.

That makes the concept important to understand as an abuse of the trust that Kerberos places in ticket issuance. In practice, the attacker is not “logging in” in the usual sense, they are presenting a forged assertion that the directory infrastructure may accept as valid.

How Golden Ticket Abuse Works

The core abuse path is straightforward: if an adversary obtains the right domain-level secret, they can create a ticket that looks legitimate to services that rely on Kerberos. The practical danger is that the forged ticket can carry elevated claims, broad access, and long-lived access that is difficult to distinguish from normal activity.

This is why Golden Ticket activity is often discussed alongside MITRE ATT&CK T1558 Steal or Forge Kerberos Tickets Guide, which separates the ticket-forgery sub-techniques and the defensive patterns that make them harder to use.

A forged Kerberos ticket also matters because it shifts the attack from a single account compromise to a domain trust compromise. Once the attacker is operating with that level of authority, individual user resets do not reliably remove the underlying access.

Exposure, Detection, and Recovery

Exposure is usually tied to the health of domain controllers, privileged directory replication paths, and the secrecy of the material used to mint Kerberos tickets. Organisations should think in terms of where that material lives, which systems can request or replicate it, and which authentication events should be present when tickets are issued or consumed.

Detection is strongest when directory and Kerberos telemetry are correlated, especially for unusual ticket lifetimes, anomalous encryption choices, and access that continues after what should have been effective account remediation. For broader identity compromise patterns, Identity Threat Detection and Response (ITDR) Guide is the best navigation point because it frames Golden Ticket use as part of a wider identity attack sequence.

Recovery is not just a password change. If the attacker obtained domain-level signing or ticket-issuing material, responders need to treat the event as a trust restoration problem and review whether the directory environment can still be relied on. That is why Golden Ticket, Silver Ticket and DCSync Guide and the krbtgt account reset guidance are directly relevant to containment and restoration.

Identity Security Consequences

Golden Ticket abuse is an identity-layer persistence mechanism because it lets an attacker keep acting as a trusted principal after the original compromise would otherwise have been contained. That can preserve access to file servers, management hosts, privileged groups, and service dependencies that trust Kerberos assertions.

The identity impact is especially serious when defenders only rotate user passwords or disable accounts. Those steps can be necessary, but they do not automatically invalidate forged tickets already in circulation or remove the attacker’s ability to mint more of them if the root material is still compromised.

For that reason, Golden Ticket scenarios belong in the same recovery conversation as credential revocation and session invalidation. The practical question is not only “who is disabled?”, but “has the trust root that enabled forged access actually been restored?”

Risk and Threat Considerations

Golden Tickets are dangerous because they turn a single high-value secret into broad, durable, and stealthy access. Attackers value them for persistence, privilege retention, and the ability to bypass the normal churn of account resets and password changes.

Failure mechanism: If the domain-level material used to forge Kerberos tickets is stolen, the attacker can mint tickets that authenticate as trusted principals even after ordinary account remediation. That failure mode is especially damaging when logging and Kerberos telemetry are weak or when the organisation assumes that user resets end the incident.

Impact: The result can be long-lived administrative access, lateral movement, repeated re-entry after cleanup, and delayed incident containment across the identity estate.

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 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1558 — Steal or Forge Kerberos TicketsGolden Ticket is a Kerberos ticket-forgery technique within ATT&CK.
Recommendation — Map ticket-forgery activity to T1558 and hunt for Kerberos abuse plus post-compromise persistence.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementGolden Ticket abuse depends on protecting and cycling the authenticating material.
AU-6 — Audit Review, Analysis, and ReportingDetection depends on reviewing Kerberos and directory audit events for anomalies.
AC-6 — Least PrivilegeThe attack becomes most damaging when excessive privileges are available to the forged ticket.
Recommendation — Rotate and manage authenticators so stolen ticket-issuing material cannot be reused. Review Kerberos and directory logs for anomalous ticket issuance and persistence indicators. Constrain privileged access paths so a forged ticket yields less reachable authority.

Practitioner Guidance

Why practitioners should care: A Golden Ticket is usually a sign that the response problem has moved from account hygiene to domain trust restoration. The responder has to determine whether the attacker only used a forged ticket or also obtained the material needed to keep forging new ones.

What to watch for: Treat repeated Kerberos anomalies, unexpected persistence after account resets, and evidence of replication or ticket-issuing abuse as signals that the environment may still be compromised. If the compromise path included directory-level secrets, focus on restoring the trust root, not just resetting visible accounts.

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