Single sign-on (SSO) is a vital cloud security technology that reduces all user application logins to one login for greater security and convenience.
What is single sign-on (SSO)?
Single sign-on (SSO) is a technology that combines several different application login screens into one. With SSO, users only have to enter their login credentials (username, password, etc.) once on a single page to access all their SaaS applications.
SSO is often used in business when an internal IT team assigns and manages user applications. Remote workers who use SaaS applications also benefit from using SSO.
Imagine if customers who had already been admitted to a bar were asked to show their identification cards to prove their age each time they attempted to purchase additional alcoholic beverages. Some customers would quickly become frustrated with the continual checks and might even try to circumvent these measures by sneaking in their drinks.
However, most establishments will only check a customer’s identification once and then serve the customer several drinks throughout the evening. This is somewhat like an SSO system: instead of establishing their identity repeatedly, a user establishes their identity once and can access several different services.
SSO is essential to many identity and access management (IAM) or access control solutions. User identity verification is crucial for knowing which permissions each user should have. Zero Trust is one example of an access control solution that integrates with SSO solutions for managing users’ identities.
What are the advantages of SSO?
In addition to being much simpler and more convenient for users, SSO is widely considered to be more secure. This may seem counterintuitive: how can signing in once with one password be more secure than multiple times with multiple passwords? Proponents of SSO cite the following reasons:
- Stronger passwords: Since users only have one password, SSO makes it easier to create, remember, and use stronger passwords.* In practice, this is typically the case: most users use stronger SSO passwords.
*What makes a password “strong”? A strong password is not easily guessed or random enough that a brute force attack is not likely to succeed. w7:g”5h$G@ is a fairly strong password; password123 is not. - No repeated passwords: When users have to remember passwords for several different apps and services, a condition known as “password fatigue” will likely set in: users will re-use passwords across services. Using the same password across several services is a huge security risk because it means that all services are only as secure as the service with the weakest password protection: if that service’s password database is compromised, attackers can use the password to hack all of the user’s other services as well. SSO eliminates this scenario by reducing all logins down to one login.
- Better password policy enforcement: With one place for password entry, SSO allows IT teams to enforce password security rules easily. For example, some companies require users to reset their passwords periodically. With SSO, password resets are easier to implement: instead of constant password resets across several different apps and services, users only have one password to reset. (While the value of regular password resets has been questioned, some IT teams still consider them an essential part of their security strategy.)
- Multi-factor authentication: Multi-factor authentication, or MFA, refers to using multiple identity factors to authenticate a user. For example, in addition to entering a username and password, a user might have to connect a USB device or enter a code that appears on their smartphone. Possession of this physical object is a second “factor” that establishes the user is who they say they are. MFA is much more secure than relying on a password alone. SSO makes it possible to activate MFA at a single point instead of starting it for three, four, or several dozen apps, which may not be feasible.
- Single point for enforcing password re-entry: Administrators can enforce re-entering credentials after a certain time to ensure the same user is still active on the signed-in device. With SSO, they have a central place to do this for all internal apps instead of enforcing it across multiple different apps, which some apps may not support.
- Internal credential management instead of external storage: Usually, user passwords are stored remotely unmanaged by applications and services that may or may not follow best security practices. With SSO, however, they are stored internally in an environment that an IT team has more control over.
- Less time wasted on password recovery: In addition to the above security benefits, SSO also cuts down on wasted time for internal teams. IT has to spend less time helping users recover or reset their passwords for dozens of apps, and users spend less time signing into various apps to perform their jobs. This has the potential to increase business productivity.
How does an SSO login work?
Whenever a user signs in to an SSO service, the service creates an authentication token that remembers verifying the user. An authentication token is a piece of digital information stored in the user’s browser or within the SSO service’s servers, like a temporary ID card issued to the user. Any app the user accesses will check with the SSO service. The SSO service passes the user’s authentication token to the app and allows the user in. If, however, the user has not yet signed in, they will be prompted to do so through the SSO service.
An SSO service does not necessarily remember who a user is since it does not store user identities. Most SSO services check user credentials against a separate identity management service.
Think of SSO as a go-between that can confirm whether a user’s login credentials match their identity in the database without managing the database themselves — somewhat like when a librarian looks up a book on someone else’s behalf based on the book’s title. The librarian does not have the entire library card catalog memorized, but they can access it easily.
How do SSO authentication tokens work?
Passing an authentication token to external apps and services is crucial in the SSO process. This enables identity verification to occur separately from other cloud services, making SSO possible.
Think of an exclusive event that only a few people are allowed into. One way to indicate that the guards at the entrance to the event have checked and approved a guest is to stamp each guest’s hand. Event staff can check every guest’s stamps to ensure they can be there. However, not just any stamp will do; event staff will know the exact shape and color of the stamp used by the guards at the entrance.
Just as each stamp has to look the same, authentication tokens have their communication standards to ensure they are correct and legitimate. SAML (Security Assertion Markup Language) is the primary authentication token standard. Similar to how webpages are written in HTML (Hypertext Markup Language), authentication tokens are written in SAML.
How does SSO fit into an access management strategy?
SSO is only one aspect of managing user access. It must be combined with access control, permission control, activity logs, and other measures for tracking and controlling user behavior within an organization’s internal systems. SSO is a crucial element of access management, however. If a system does not know who a user is, there is no way to allow or restrict that user’s actions.
