Golden SAML
Qu'est-ce que Golden SAML ?
Golden SAMLAn identity-attack technique that steals a federation IdP's token-signing private key (typically from AD FS) and forges arbitrary SAML responses, granting persistent, MFA-bypassing access to any federated service.
Golden SAML was disclosed by CyberArk Labs in 2017 and shot to prominence as a documented technique used in the 2020 SolarWinds-Sunburst intrusions. The attack assumes a federated identity model: an on-premises identity provider (most often Microsoft AD FS) signs SAML responses with a private token-signing key whose public counterpart is trusted by every relying party — Microsoft 365, AWS, Salesforce, Workday, and so on. An attacker who reaches AD FS with sufficient privilege (Domain Admin, AD FS service account) can extract that private key and then sign SAML responses for any user, any group memberships, with no need to log in to the IdP at all. Because the resulting tokens are cryptographically valid, MFA prompts, password resets, and account lockouts are bypassed; revocation requires rotating the token-signing certificate and re-establishing trust with every relying party. Defensive controls focus on hardening AD FS (HSM-backed signing keys, restricted Tier-0 access, monitoring of `Microsoft-Windows-Security-Auditing` 410/411 events), migrating to cloud-native IdPs (Entra ID with no AD FS), and detecting anomalous SAML assertions at relying parties (e.g. impossible NameID claims, unfamiliar issuers, sudden first-seen IPs).
● Exemples
- 01
The Sunburst actors used Golden SAML to mint cloud tokens for arbitrary Microsoft 365 users from compromised on-premises AD FS without further authentication.
- 02
An organization migrates from AD FS to Entra ID pass-through authentication, eliminating the on-prem token-signing key as a Tier-0 single point of compromise.
● Questions fréquentes
Qu'est-ce que Golden SAML ?
An identity-attack technique that steals a federation IdP's token-signing private key (typically from AD FS) and forges arbitrary SAML responses, granting persistent, MFA-bypassing access to any federated service. Cette notion relève de la catégorie Identité et accès en cybersécurité.
Que signifie Golden SAML ?
An identity-attack technique that steals a federation IdP's token-signing private key (typically from AD FS) and forges arbitrary SAML responses, granting persistent, MFA-bypassing access to any federated service.
Comment fonctionne Golden SAML ?
Golden SAML was disclosed by CyberArk Labs in 2017 and shot to prominence as a documented technique used in the 2020 SolarWinds-Sunburst intrusions. The attack assumes a federated identity model: an on-premises identity provider (most often Microsoft AD FS) signs SAML responses with a private token-signing key whose public counterpart is trusted by every relying party — Microsoft 365, AWS, Salesforce, Workday, and so on. An attacker who reaches AD FS with sufficient privilege (Domain Admin, AD FS service account) can extract that private key and then sign SAML responses for any user, any group memberships, with no need to log in to the IdP at all. Because the resulting tokens are cryptographically valid, MFA prompts, password resets, and account lockouts are bypassed; revocation requires rotating the token-signing certificate and re-establishing trust with every relying party. Defensive controls focus on hardening AD FS (HSM-backed signing keys, restricted Tier-0 access, monitoring of `Microsoft-Windows-Security-Auditing` 410/411 events), migrating to cloud-native IdPs (Entra ID with no AD FS), and detecting anomalous SAML assertions at relying parties (e.g. impossible NameID claims, unfamiliar issuers, sudden first-seen IPs).
Comment se défendre contre Golden SAML ?
Les défenses contre Golden SAML combinent habituellement des contrôles techniques et des pratiques opérationnelles, comme détaillé dans la définition ci-dessus.
Quels sont les autres noms de Golden SAML ?
Noms alternatifs courants : Golden SAML attack.
● Termes liés
- identity-access№ 1073
SAML
Standard ouvert basé sur XML pour échanger des assertions d'authentification et d'autorisation entre un fournisseur d'identité et un fournisseur de service.
- identity-access№ 1162
Authentification unique (SSO)
Mécanisme d'authentification permettant à un utilisateur de se connecter une seule fois auprès d'un fournisseur d'identité de confiance pour accéder ensuite à plusieurs applications sans ressaisir d'identifiants.
- identity-access№ 453
Identité fédérée
Architecture dans laquelle plusieurs organisations ou domaines font confiance à un fournisseur d'identité commun afin que les utilisateurs réutilisent la même identité partout.
- identity-access№ 014
Active Directory
Service d'annuaire d'entreprise de Microsoft pour les réseaux Windows, qui assure l'authentification, l'autorisation et la gestion centralisée des stratégies pour utilisateurs, machines et ressources.
- identity-access№ 652
Kerberos
Protocole d'authentification réseau à base de tickets utilisant la cryptographie symétrique et un Centre de Distribution de Clés de confiance pour offrir une authentification unique sécurisée.
- cloud-security№ 202
Cloud Control Plane Attack
An attack that targets the management API of a cloud provider (AWS, Azure, GCP) — IAM, billing, deployment APIs — rather than workloads, achieving tenant-wide impact through stolen tokens, federation abuse, or partner-channel compromises.