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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Single Sign-On (SSO)?

Single sign-on (SSO) is an authentication method that lets users log in once with a central identity provider and then access multiple applications without signing in again.

Illustration for the cybersecurity term Single Sign-On (SSO)
Home / Blog / Cybersecurity Terms / What Is Single Sign-On (SSO)?
17 November 2026

What Is Single Sign-On (SSO)?

What Is Single Sign-On (SSO)?

Single sign-on (SSO) is an authentication approach that allows a user to sign in once, with one set of credentials, and then reach many different applications without logging in to each one separately. Behind the scenes, a central identity provider confirms who the user is and passes that confirmation securely to each application.

For employees, SSO means fewer passwords to remember and fewer login prompts. For security teams, it means one place to enforce strong authentication, apply access policies, and switch off access when someone leaves. Done well, it improves both convenience and security at the same time, which is rare.

How SSO Works

SSO relies on a trust relationship between two parties:

When a user opens an application, it redirects them to the identity provider. If they already have an active session, the IdP issues a signed token or assertion straight away; if not, it asks them to authenticate first, typically with a password and multi-factor authentication. The application verifies the signature on the token and logs the user in without ever seeing their password.

Common SSO Protocols

ProtocolTypical useNotes
SAML 2.0Enterprise web applicationsXML-based assertions, widely supported by business software
OpenID ConnectModern web and mobile appsIdentity layer built on OAuth 2.0, uses JSON Web Tokens
OAuth 2.0Delegated authorisation for APIsGrants access to resources, not designed for authentication on its own
KerberosOn-premises Windows networksTicket-based SSO inside Active Directory domains

Security Benefits

Risks to Manage

Concentrating authentication in one place also concentrates risk. If an attacker compromises a user’s SSO session, they may gain access to every connected application. If they compromise the identity provider itself, the impact can be enormous.

Real incidents illustrate this. In the SolarWinds campaign uncovered in December 2020, attackers used a technique known as Golden SAML, stealing the signing key from an on-premises federation server to forge authentication tokens for cloud services. In October 2023, Okta disclosed that attackers had accessed its customer support system and obtained files that included session tokens belonging to some customers.

Other risks include stolen session cookies, which bypass MFA entirely and are closely related to session hijacking, and applications left outside SSO that still use local passwords.

Securing an SSO Deployment

SSO and Provisioning

SSO handles authentication, but users also need accounts created and removed in each application. Standards such as SCIM (System for Cross-domain Identity Management) automate this, so that joiners receive access on day one and leavers lose it immediately. Combined with role-based access control, this makes access management far more reliable than manual processes.

At Privia Security, our Multi-Factor Authentication (2FA) Solutions strengthen your SSO sign-ins, and our penetration tests assess how attackers could abuse your identity platform.

FAQ – Frequently Asked Questions

Is Single Sign-On Secure?

SSO is generally more secure than separate passwords for every application, because it reduces password reuse and lets you enforce strong MFA and access policies in one place. However, it does concentrate risk, so the identity provider, its administrator accounts, and its signing keys must be protected very carefully and monitored closely.

What Is the Difference Between SSO and MFA?

SSO is about convenience and central control: one login gives access to many applications. MFA is about the strength of that login: it requires two or more independent factors. The two work best together, with MFA enforced at the identity provider so that every application connected through SSO benefits from strong authentication.

What Is the Difference Between SAML and OpenID Connect?

Both enable SSO. SAML 2.0 is an older, XML-based standard widely used by enterprise web applications. OpenID Connect is a newer identity layer built on OAuth 2.0, using JSON Web Tokens, and it is better suited to modern web, mobile, and API-driven applications. Many identity providers support both protocols.

What Happens If the Identity Provider Goes Down?

If the identity provider is unavailable, users may be unable to sign in to any connected application, so resilience planning matters. Cloud identity providers offer high availability, and organisations should keep secured emergency access accounts and documented procedures for outages, tested as part of business continuity planning.

Related Terms

You May Be Interested In These

What Is Secure Boot?

Cybersecurity Terms

17 November 2026

What Is Secure Boot?

Read More
What Is Kubernetes RBAC Privilege Escalation?

Cybersecurity Terms

17 November 2026

What Is Kubernetes RBAC Privilege Escalation?

Read More