Single Sign-On (SSO)

Single sign-on lets staff sign in once, with one company account, and then reach many separate apps without logging in to each one. A central identity provider checks who they are and vouches for them to each app.

IntermediateCategory: Passwords, authentication and identity

Also called: SSO, federated sign-on, identity provider

With single sign-on (SSO), a company's identity provider, such as Microsoft Entra ID, Google Workspace or Okta, handles every sign-in. When a user opens a connected app, the app sends them to the identity provider, which confirms who they are and passes back a signed message saying so. Standards such as SAML and OpenID Connect carry that message.

The security benefits are significant:

  • One place to enforce strong sign-in. Multifactor authentication and device checks are set once and apply to every connected app.
  • Faster offboarding. Disabling one account cuts access to everything when someone leaves.
  • Fewer passwords. Staff are less likely to reuse weak passwords across services.

The trade-off is concentration of risk. If an attacker takes over an SSO account, or finds a flaw in how an app checks SSO messages, they can reach many systems at once. Protect SSO accounts with phishing-resistant MFA and watch for unusual sign-ins.

A managed security provider can monitor identity provider logs for signs of account takeover.

Related terms

Sources

  1. SAML 2.0 Technical Overview (OASIS)
  2. Glossary: SAML SSO (NIST)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.