Single Sign-On (SSO)

Technical explanation

An authentication arrangement that allows a user to access multiple applications through one identity-provider session. The control should be based on identified threats, least privilege, strong identity, logging, monitoring and tested response procedures. Effectiveness depends on implementation and operating context rather than the presence of a product label.

Business relevance

It reduces the likelihood or impact of unauthorised access, data loss and service disruption and provides evidence for assurance.

Implementation example

A cross-functional team applies Single Sign-On (SSO) in a production initiative, defines ownership and success criteria, tests representative scenarios, monitors outcomes and records corrective actions before scaling.

Limitations and common misconceptions

No single control eliminates risk. Misconfiguration, compromised identities, weak recovery and changing threats require defence in depth and continuous review.

Topics

Sources