Posture check · Account security
Privileged account with a service principal name (T1558.003)
Any domain user can request a service ticket for this account and crack its password offline (Kerberoasting). Group managed service accounts (gMSAs) are excluded.
Why it matters
The cracking happens offline, where no failed authentication is logged. A cracked password hands over this account's privileges.
How GraphnAI finds it
It runs after every sync, on each connected domain or tenant on its own. It applies to Active Directory.
It reads:
- The directory attributes
servicePrincipalNameandobjectClass - The privilege tier classification
Tiered Fidelity™ level: Theoretical
Every finding from this check carries the Theoretical level.
- TheoreticalThis checkConfigured in the directory. Nothing else checked.
- ConstrainedA constraint on it has been checked.
- ValidatedTelemetry has seen it in use.
How Select Fire™ fixes it
How to fix it
Remove the service principal name if the account isn't a service, or move the service to a group managed service account (gMSA). If it must keep the SPN, use AES and a password of 25 or more characters.
What Select Fire changes
Select Fire opens from the finding and simulates each change on your live graph before anything changes in your directory.
- Remove service principal name For user accounts and service accounts.Semi-Auto: you authorize each change. Full-Auto never runs it.
Removing a service principal name stops Kerberos service tickets being issued for that service. Confirm the service owner before removing it.
If someone uses it
This detection rule raises an alert when the attack this exposure invites shows up in your domain controllers' events.
Related checks
MITRE ATT&CK® technique names and MITRE D3FEND™ technique labels: © The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. ATT&CK® is a registered trademark and D3FEND™ a trademark of The MITRE Corporation.
See it on your own directory.
The Public Preview is free for 30 days from your first sync, on your own server.