Kerberoasting Check
Identifies accounts with Service Principal Names (SPNs) whose Kerberos service tickets can be requested and cracked offline, and flags any of those accounts that are also privileged.
Prerequisite
Requires a valid Standard User account (authenticated).
Commands run
ad-kit runs Impacket
GetUserSPNs.py -request:
What it checks
ad-kit enumerates SPN-associated accounts and requests their Kerberos service tickets, then cross-references the results against the monitored privileged groups.
How it works
An SPN maps a Kerberos service instance to a sign-in account. Any authenticated domain user can request a service ticket (TGS) for an SPN, and the ticket is encrypted with a key derived from the service account's password, so it can be cracked offline.
Modern environments often attach services to machine accounts or managed service accounts, whose strong secrets rotate automatically and are hard to crack. The risk is higher where a standard user account holds one or more SPNs, because that password's strength and rotation depend on manual management.
Why it matters
A weak service-account password can be recovered offline and reused as a valid domain credential. When the SPN is on a privileged account, recovery can give immediate, high-impact access.
See Kerberoasting for the full attack flow.
Findings
| Finding ID | Title |
|---|---|
| KERB-001 | Kerberoastable Accounts Identified |
| KERB-002 | Service Principal Names Assigned to Privileged Accounts |
Tooling
- Impacket:
GetUserSPNs.py -request(used by this check). - NetExec:
--kerberoasting. - Rubeus:
kerberoast. - targetedKerberoast: set-SPN variant.
- hashcat:
hashcat -m 13100.