Identity Federation
Also called Identity broker, SSO federation.
Trusting an external identity provider to authenticate users into the cloud.
What it is
An arrangement where a cloud environment trusts an external identity provider, via standards such as SAML or OIDC, to authenticate users and assert their identity rather than maintaining separate local accounts. A broker translates that external assertion into cloud access.
Why it matters
Federation centralizes authentication but also makes the identity provider a high-value target, since compromising it or its trust configuration can mint access into every connected environment.
In practice
An investigator examines whether forged federation assertions, not stolen passwords, are how the attacker logged in as multiple users.
What to look for
- Changes to federation trust, signing certificates or identity provider settings.
- Tokens issued with unusual claims or lifetimes.
- Logins that skip MFA because the provider vouched for them.
Common mistake
Securing the cloud side only. If the identity provider is compromised, every trusting app is too.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Entra ID Protection Commercial
Scores sign-in and user risk in Microsoft Entra ID and can force MFA or a reset.
-
Okta Identity Threat Protection Commercial
Evaluates session risk continuously and can end sessions when it changes.
-
BloodHound Open source
Maps attack paths through Entra ID and Active Directory relationships.
Read next
- Illicit OAuth Grant: Tricking a user into authorizing a malicious app's access to their account.
- Role Assumption: Temporarily taking on a role's permissions to act as a different identity.
- Identity and Access Management: The system of identities, roles, and policies that gates access to cloud resources.