Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Federated Identity Management?

Federated identity management lets one organisation vouch for a user to another, so people authenticate once at home and are recognised everywhere that trust reaches.

Illustration for the cybersecurity term Federated Identity Management
Home / Blog / Cybersecurity Terms / What Is Federated Identity Management?
17 November 2026

What Is Federated Identity Management?

What Is Federated Identity Management?

Federated identity management is an agreement between parties, expressed in cryptography. One party—the identity provider—runs the authentication, knows the user, and asserts facts about them. The other party—the relying party or service provider—does not know the user at all, holds no password for them, and accepts the assertion because it trusts the issuer and can verify the signature.

The practical result is that a researcher at a UK university signs in once and reaches a publisher’s archive, a supplier’s engineer opens a document in your tenant without you creating a password for them, and a staff member moves between forty cloud applications without forty sets of credentials.

Federation Is Not the Same as Single Sign-On

The two get conflated, and the distinction is useful. Single sign-on is the user experience: authenticate once, reach many applications. Federation is the trust architecture that makes that work across organisational boundaries. You can have single sign-on without federation, inside one directory, and you can federate without a seamless user experience.

What federation specifically adds is a boundary. The identity provider is in one administrative domain, the service in another, and the only thing crossing between them is a signed assertion containing the claims that were agreed in advance.

The Protocols

A fourth category matters operationally: cross-tenant federation inside a single platform, such as Microsoft Entra ID B2B collaboration or AWS identity federation between accounts. The protocol is handled for you, but the trust decision is yours and it is just as consequential.

The Claims Conversation

Most federation projects fail on attributes rather than cryptography. The service provider needs to know not only who the user is but what they are entitled to, and that means agreeing which claims travel, in what format, and from which authoritative source.

Three decisions deserve explicit attention. First, the identifier: use a stable, non-reassignable value rather than an email address, because email addresses change on marriage and get recycled when staff leave. Second, data minimisation—every claim sent to a third party is personal data disclosed to them, and UK GDPR expects you to send only what is necessary, so a service that asks for full HR attributes when it needs a department code should be challenged. Third, authorisation: decide whether group membership travels in the assertion or whether the service holds its own mapping, because the first makes your directory the control plane and the second creates a second place where leavers must be removed.

Governing the Trust

Every federation relationship is a standing grant that outlives the project that created it. Three controls keep that manageable.

Keep a register of federated relationships with a named business owner, a purpose, the claims released, and a review date. In practice most organisations discover, when they first build this, several trusts to services nobody uses and at least one to a supplier whose contract ended.

Treat trust configuration as privileged change. Adding a federated domain, registering a new issuer certificate, or altering a claims transformation rule changes who can authenticate as whom, and those changes are a known persistence technique. Alert on all of them, and review them with the same seriousness as membership of an administrative group. Our entry on identity provider federation risks goes into the specific attacks.

Finally, plan for the failure modes. Certificates expire, and an expired signing certificate takes down authentication for every federated service at once—track renewal dates centrally rather than trusting each service owner to notice. Incoming federation from partners needs conditional access of its own, because an external organisation’s authentication standards are not yours. And when a federation ends, remove the trust rather than leaving it dormant, since a dormant trust with a valid certificate is still a working route in.

At Privia Security, we assess federation architecture and trust governance through our infrastructure and architecture review services.

FAQ – Frequently Asked Questions

What Is the Difference Between Federation and Single Sign-On?

Single sign-on describes the experience of authenticating once and reaching many applications. Federation describes the trust architecture that allows one organisation’s identity provider to vouch for a user to a different organisation’s service. Federation usually delivers single sign-on, but single sign-on can also exist inside one directory with no federation at all.

Should We Use SAML or OpenID Connect?

Use OpenID Connect for anything new, especially mobile applications and single-page applications, because it is JSON-based, better specified for public clients, and supported by modern libraries. Use SAML where the service provider only offers it, which still covers a great deal of enterprise and academic software. Many organisations run both, with the identity provider handling the translation.

What Should Travel in a Federation Assertion?

A stable identifier that is never reassigned, plus the minimum set of attributes the service genuinely needs. Avoid using email address as the identifier, since it changes and gets recycled. Under UK GDPR each released attribute is a disclosure of personal data to the service provider, so challenge requests for broad attribute sets and record what you agreed to release.

How Do We Stop Federation Trusts Accumulating?

Maintain a register with a named business owner, the purpose, the claims released, and a review date for every relationship, and tie it to contract end dates. Alert on any change to federated domains, issuer certificates, or claims rules, since those changes are a known persistence technique. Remove ended relationships rather than leaving them dormant with valid certificates.

Related Terms

You May Be Interested In These

What Is Service Mesh Security?

Cybersecurity Terms

17 November 2026

What Is Service Mesh Security?

Read More
How Do You Investigate a Suspicious Email?

Cybersecurity Terms

17 November 2026

How Do You Investigate a Suspicious Email?

Read More
What Is UN R155 Automotive Cybersecurity?

Cybersecurity Terms

17 November 2026

What Is UN R155 Automotive Cybersecurity?

Read More