Skip to content

AD-SPN-13: No domain admin accounts should have SPNs configured

ID AD-SPN-13
Severity Critical
Suite Active Directory (on-premises)
Product Active Directory
Feature Service principal names
Security area Privileged access
Resource type User
User impact of fixing Low
Effort to fix Medium
Framework controls nist-800-53-r5:AC-6(5) Least Privilege | Privileged Accounts
nist-800-53-r5:IA-5 Authenticator Management
MITRE ATT&CK T1558.003
Reads from On-premises Active Directory

Detailed visibility into domain admin SPNs is critical for security incident response:

  • Immediate remediation: Know exactly which SPNs to remove
  • Service identification: Understand what services were improperly configured
  • Attack surface assessment: Evaluate the scope of exposure
  • Compliance violation: Domain admins should never have SPNs

Any SPN on a domain admin account is a critical finding requiring immediate action.

Preventive

Immediate actions required:

  1. Remove ALL SPNs from domain administrator accounts
  2. Investigate how and why SPNs were configured
  3. Create dedicated service accounts or gMSAs for the services
  4. Review domain admin membership and remove unnecessary accounts
  5. Implement monitoring for SPN changes to privileged accounts
  6. Consider this a potential security incident requiring investigation

This test identifies domain administrator accounts and provides detailed information about any SPNs configured on them, including service class, host, FQDN status, and full SPN value for remediation.

  • Test-MtAdUserSpnDomainAdminCount - Counts SPNs on domain admins
  • Test-MtAdUserSpnTotalCount - Overall user SPN analysis
  • Test-MtAdUserSpnUnknownDetails - Unknown SPN details on all users

Mito check. Author: soulemike. Open-source licences.

Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).

© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.