Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1558_steal-or-forge-kerberos-tickets
Adversaries may attempt to subvert Kerberos authentication by stealing or forging Kerberos tickets to enable Pass the Ticket.
Passed 21 of 23 test cases with the skill, and 13 of 23 without it.
and 5 more in the full report
8 fixed13 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What single specific Common Weakness Enumeration (CWE) identifier is assigned to Kerberos ticket theft and forgery in the technique's risk mapping?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies CWE-522 as the sole CWE category | Missed | Passed |
The instructions your model reads when the skill loads.
Adversaries may attempt to subvert Kerberos authentication by stealing or forging Kerberos tickets to enable Pass the Ticket. Kerberos is an authentication protocol widely used in modern Windows domain environments. In Kerberos environments, referred to as “realms”, there are three basic participants: client, service, and Key Distribution Center (KDC). Clients request access to a service and through the exchange of Kerberos tickets, originating from KDC, they are granted access after having successfully authenticated. The KDC is responsible for both authentication and ticket granting. Adversaries may attempt to abuse Kerberos by stealing tickets or forging tickets to enable unauthorized access.
On Windows, the built-in klist utility can be used to list and analyze cached Kerberos tickets.
Platforms: Windows, Linux, macOS
Identify Attack Surface: Determine if the target environment is susceptible to Steal or Forge Kerberos Tickets by examining the target platforms (Windows, Linux, macOS).
Assess Existing Defenses: Review whether mitigations for T1558 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
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.
test cases passed, vs 13 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.