Azure AD: Federated identity credential addition to service principal
Adversaries may abuse Entra ID federated identity credentials to establish persistent, secretless authentication by pointing credentials to a controlled OIDC issuer.
Triage facts
Revision 1- Applicability
- Entra ID
- Evidence
- Unknown
- Severity
- Medium
- Action
- Elevated
- Sources
- 3 public sources
- Freshness
- Revision 1Nov 3, 15:16 UTC
- Source quality
- A1Likely
Attackers can leverage the Entra ID (formerly Azure AD) workload identity federation feature to gain persistent access to service principals. By adding a new federated identity credential that points to an attacker-controlled OIDC issuer, a threat actor can authenticate as the service principal without requiring client secrets. This technique evades standard secrets monitoring and persists across credential rotations.
Impact
Successful exploitation grants an attacker a persistent, secretless authentication path to the target service principal, potentially allowing for lateral movement, privilege escalation, or access to cloud resources protected by the service principal identity.
Recommendation
- Baseline existing federated identity credentials across all service principals to identify legitimate OIDC configurations.
- Implement monitoring for the addition of new federated identity credentials, specifically focusing on unknown or unapproved OIDC issuers.
- Audit existing service principals for overly permissive subject claims in federated credentials.
- Use the hunt lead provided in the action plan to investigate current environment activity.
Threat Hunt
Search Azure AD AuditLogs for operations 'Update application' or 'Update service principal' where the modifiedProperty displayName is 'FederatedIdentityCredentials'.
Data: Azure Active Directory AuditLogs
Mitigations
Review all service principals with federated identity credentials and verify the OIDC issuers against a list of approved providers.
T1098.001