Golden Ticket T1558.001
- Tactic
- Credential Access
- Platform
- Windows
- Version
- 1.2
- Created
- 11 February 2020
- Last modified
- 24 October 2025
- Contributor
- Itamar Mizrahi, Cymptom
Golden Ticket MITRE reference T1558.001
1 group has been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
All 1 groups for this technique
4 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can forge a ticket-granting ticket.1
Incorporates the Rubeus framework to allow for Kerberos ticket manipulation, specifically for forging Kerberos Golden Tickets.1
Can leverage its implementation of Mimikatz to obtain and use golden tickets.1
All 4 software entries for this technique
Offense vs defense T1558.001
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Golden Ticket detection strategy DET0144
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detect Forged Kerberos Golden Tickets (T1558.001)
AN0405 · Windows
Detects forged Kerberos Golden Tickets by correlating anomalous Kerberos ticket lifetimes, unexpected encryption types (e.g., RC4 in modern domains), malformed fields in logon/logoff events, and TGS requests without preceding TGT requests. Also monitors for abnormal patterns of access associated with elevated privileges across multiple systems.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process AccessDC0035 | WinEventLog:Sysmon | EventCode=10 |
| Active Directory Credential RequestDC0084 | WinEventLog:Security | EventCode=4769 |
| Logon Session MetadataDC0088 | WinEventLog:Security | EventCode=4672, 4634 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TicketLifetimeThreshold | Kerberos TGT ticket lifetime exceeding default domain duration; tunable to environment-specific policies. |
| AllowedEncryptionTypes | Valid encryption algorithms for Kerberos tickets; anomalies (e.g., RC4) may indicate forgery. |
| PrivilegedAccountPatterns | Baseline of privileged accounts expected to perform Kerberos operations; deviations indicate suspicious activity. |
| ProcessAllowlist | Expected processes interacting with lsass.exe; deviations may indicate credential dumping. |
For containing the impact of a previously generated golden ticket, reset the built-in KRBTGT account password twice, which will invalidate any existing golden tickets that have been created with the KRBTGT hash and other Kerberos tickets derived from it. For each domain, change the KRBTGT account password once, force replication, and then change the password a second time. Consider rotating the KRBTGT account password every 180 days.
Limit domain admin account permissions to domain controllers and limited servers. Delegate other admin functions to separate accounts.
Tests from Atomic Red Team (MIT licence) · technique definition