Can create silver tickets.1
Silver Ticket T1558.002
- Tactic
- Credential Access
- Platform
- Windows
- Version
- 1.1
- Created
- 11 February 2020
- Last modified
- 24 October 2025
Adversaries who have the password hash of a target service account (e.g. SharePoint, MSSQL) may forge Kerberos ticket granting service (TGS) tickets, also known as silver tickets. Kerberos TGS tickets are also known as service tickets.[1]
Silver Ticket MITRE reference T1558.002
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 be used to forge Kerberos tickets using the password hash of the AZUREADSSOACC account.1
Can leverage its implementation of Mimikatz to obtain and use silver tickets.1
All 4 software entries for this technique
Offense vs defense T1558.002
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.
Silver Ticket detection strategy DET0241
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 Silver Tickets (T1558.002)
AN0675 · Windows
Detects forged Kerberos Silver Tickets by identifying anomalous Kerberos service ticket activity such as malformed fields in logon events, TGS requests without interaction with the KDC, and access attempts using service accounts outside expected hosts/resources. Also monitors suspicious processes accessing LSASS memory for credential dumping.
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:Kerberos | Kerberos TGS-REQ anomalies without KDC validation (Silver Ticket behavior) |
| 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 |
|---|---|
| ServiceAccountScope | Expected mapping of service accounts to specific resources; deviations may indicate Silver Ticket use. |
| TicketValidationBaseline | Expected TGS issuance patterns including KDC validation; anomalies may signal forged tickets. |
| ProcessAllowlist | Known processes that legitimately interact with LSASS; others may indicate dumping attempts. |
| TimeWindow | Correlate Kerberos requests within a tunable timeframe to reduce false positives. |
Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.
Ensure strong password length (ideally 25+ characters) and complexity for service accounts and that these passwords periodically expire. Also consider using Group Managed Service Accounts or another third party product such as password vaulting.
Limit service accounts to minimal required privileges, including membership in privileged groups such as Domain Administrators.
Tests from Atomic Red Team (MIT licence) · technique definition