GUIDE · IDENTITY AND ACCESS

Single sign-on (SSO): benefits, risks and how to implement it

This guide explains what single sign-on, or SSO, does, which benefits it brings to people who use applications and to the IT department, and which new risks it introduces. By the end you will be able to prepare the implementation, choose which applications to connect first and check that the connection is genuinely secure.

Updated october 2026
6 min read
Altovar Technical Editorial Team

1. What single sign-on is

Single sign-on, abbreviated as SSO, is a mechanism that gives access to several applications with one login. The person authenticates once with a central identity service, and the connected applications trust that confirmation instead of asking for a new password. For the user, this means fewer sign-in screens and fewer passwords to remember.

It should not be confused with the habit of using the same password everywhere, which is the opposite of security. SSO works because there is a single source of truth for identity, and applications delegate verification to that source. This same strength creates the main risk, which we come to later.

2. Concrete benefits for the organisation

The first benefit is fewer passwords. Every application with its own password is a point where a user can make a mistake, reuse it or write it down. With single sign-on the credentials to manage decrease, and so do support requests for password resets. The second benefit is revocation: when a person leaves the organisation, disabling one account blocks access to all connected applications.

The third benefit is visibility. The central service records who signs in, from where and with which method, and this data is useful for spotting unusual behaviour. The fourth concerns consistent policies, such as second-factor authentication or blocking access from unexpected networks, which are applied in one place instead of system by system.

3. Risks to manage

The main risk is concentration. If the central identity is compromised, all connected applications are exposed together. For this reason the identity service must be treated as the most critical system in the organisation: restricted administrative access, monitoring of changes, backup copies of its configuration and tested recovery procedures.

A second risk is sessions that last too long. If single sign-on keeps sessions active for a long time, a device left unlocked opens everything. A third is poor trust configuration: a connected application with incorrect settings may accept identities that were never intended. The connection must therefore be verified, not just switched on.

4. Prerequisites before you start

Before connecting any application you need a reliable identity service, a list of applications with their owners and a decision on who administers the connection. You also need a plan for applications that do not support the single sign-on standard, because there will almost always be some. The most widespread protocols are standards such as SAML and OpenID Connect, but compatibility must be verified application by application.

  • A central identity service with up-to-date users
  • A list of applications with owner and sensitivity level
  • A contact for each application who approves the connection
  • A plan for applications without standard support
  • A policy for session duration

5. How to implement it, step by step

Implementation works best in phases, starting with a low-risk application to learn the procedure. The sequence below is a starting point to adapt to your environment.

  1. Choose a first, non-critical application and connect it in a test environment, with a small pilot group of users.
  2. Configure trust between the identity service and the application, checking that the information exchanged is what you expect.
  3. Verify the full flow: sign-in, normal use, session expiry and disabling a test account.
  4. Set up the second factor and access rules in the identity service before extending the connection.
  5. Connect the other applications in order of importance, documenting the owner and settings for each.
  6. Retire old local passwords only once the connection is stable, and tell people in advance.

6. Common mistakes to avoid

The first mistake is connecting applications without verifying deactivation. An application that keeps a parallel local access defeats central revocation. The second is leaving emergency accounts unchecked, used to bypass the connection when something goes wrong. The third is failing to communicate: people react by changing passwords or looking for shortcuts if they do not understand the new flow.

The fourth is treating SSO as a finished project once the first connection is made. Applications change, suppliers update their protocols and new systems come into use. An up-to-date list of connections and a periodic review are needed.

7. How to check that it works

A useful check does not stop at confirming that sign-in happens. Verify that disabling a test account really blocks all connected applications, that session expiry is enforced and that failed attempts are logged. Also verify that applications do not accept direct access with local credentials when policy forbids it.

  • Disabling a test account across all applications
  • Session expiry and a new sign-in required
  • Failed attempts recorded in the central service
  • No parallel local access

8. How to start

This week, list the applications most used by staff and ask each supplier whether it supports single sign-on using recognised standards, and under what conditions. Then choose a single low-risk pilot application. With these answers you can decide the order of connection without committing yet to a large project.

Frequently Asked Questions

Are SSO and multi-factor authentication the same thing?

No. SSO decides how you access several applications with a single login, while multi-factor authentication decides how many proofs are needed to demonstrate identity. They are complementary: central login is more secure when it also requires a second factor, because all connected applications benefit together.

Do all applications support single sign-on?

No. Many modern applications do, but some older management systems and specialised tools do not offer a standard connection. For these cases there are intermediate solutions, such as access through a mediation service, or a documented separate login subject to more frequent checks. Check with the supplier before planning.

What happens if the identity service is unavailable?

Connected applications cannot verify new sessions, so access stops. For this reason the service must be designed with redundancy and a written emergency procedure that defines who can authorise temporary access and how it is recorded. Ask your supplier how the service behaves in a failure and what availability commitments it offers.

Does SSO really reduce the IT department's workload?

Yes, in the medium term, especially for password resets and access revocation. In the short term the workload may increase, because there are connections to configure, verify and document. The benefit grows with the number of applications, but only if the connection process is governed and not left to individual initiative.

Do external users need to be managed differently?

Often, yes. Suppliers and external collaborators have different roles and timeframes from internal staff, and must be managed with dedicated identities and explicit expiry dates. An external identity should not have access to the same applications as staff without a specific assessment, and the connection must be reviewed when the working relationship ends.

Is SSO required by regulation?

No regulation specifically lists this tool. However, GDPR and NIS2 require security measures appropriate to the risk, and access control falls within that framework. Single sign-on can help demonstrate this, if it is well governed. Which solution is appropriate in your case should be assessed with a consultant.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →