Posture check · Workload and agent identity
Privileged service principal authenticates with a secret
A privileged app can sign in with a client secret, a password that can be copied and replayed from anywhere.
Why it matters
Secrets end up in scripts, pipelines and configuration files. A certificate or a federated credential is much harder to steal and reuse.
How GraphnAI finds it
It runs after every sync, on each connected domain or tenant on its own. It applies to Microsoft Entra ID.
It reads:
- The directory attributes
servicePrincipalType,keyCredentials,passwordCredentials,credentialsInheritedFromApp,appOwnerOrganizationId,appOwnerClassandverifiedPublisher - 4 more GraphnAI analyses
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.
Why there's no automatic fix
Removing a service principal's credential, or disabling the service principal, is done in Microsoft Entra.
How to fix it
This privileged app signs in with a secret. Switch it to a certificate or a federated credential, then remove the secret.
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.