SSO, SAML, SCIM and MFA Explained for Buyers
Security · 10 min read ·
Single sign-on, SAML, OpenID Connect, SCIM and MFA in plain terms, and how to state access-control features accurately on a specification page.
Four acronyms dominate the access-control section of any business software specification: SSO, SAML, SCIM and MFA. Buyers ask for them by name. Vendors list them as checkboxes. Between the two, meanings blur, and a feature that is listed may not be the feature the buyer wanted. This guide explains each term in plain language, shows how they fit together, and gives wording for stating them accurately.
If you read specification pages for a living, treat it as a glossary. If you write them, treat it as a style guide.
The problem these features solve
When a company adopts many tools, each with its own usernames and passwords, three problems appear. People reuse weak passwords. New joiners need accounts creating in a dozen places. Leavers keep access somewhere because nobody remembered to remove it. Access-control features exist to move those jobs to a single place where they can be done properly.
The central idea is an identity provider: a system that holds the organisation's user accounts and proves who someone is. The business software then trusts the identity provider's word instead of keeping its own list of passwords.
Single sign-on
Single sign-on, usually abbreviated SSO, is the arrangement in which a user authenticates once with the identity provider and is then granted access to several applications without signing in to each separately. In practice a person visits the product, is redirected to their organisation's sign-in page, completes it there and is sent back signed in.
The benefits are straightforward: fewer passwords, central enforcement of security rules and faster off-boarding, because disabling an account at the identity provider cuts access everywhere.
What SSO is not: it is not automatic provisioning of accounts, and it is not by itself a guarantee of strong authentication. Those belong to SCIM and to the identity provider's policies respectively.
SAML and OpenID Connect
SSO needs a protocol, a set of rules for how the product and the identity provider exchange the proof of identity. Two are widely used.
SAML, the Security Assertion Markup Language, is an XML-based standard in which the identity provider sends the product a signed statement, called an assertion, saying who the user is and possibly some attributes such as their group memberships. It is long established and common in enterprise software.
OpenID Connect is a newer layer built on top of OAuth 2.0 which uses JSON web tokens to carry the same kind of information. It is common in modern web and mobile applications.
A specification that says only "SSO supported" leaves the question of protocol open, and buyers whose identity provider supports only one will need the answer. State which protocols you support and which identity providers you have tested with.
SCIM
The System for Cross-domain Identity Management, known as SCIM, is a standard for automating the exchange of user identity information between identity systems. In everyday terms it lets the identity provider tell the product, automatically, "create this user", "update their details" or "remove them".
Where SSO answers "how does this person sign in?", SCIM answers "does this person have an account at all, and with what attributes?". Without SCIM, an organisation that uses SSO still has to create accounts by hand, and may leave an account in place after the person has left. The account would be unusable through SSO, but it might still hold data, consume a paid seat or have an active access token.
If you support SCIM, say which operations: create, update, deactivate, delete, group sync. Say whether deactivation preserves the user's data and how the vendor handles seats.
Multi-factor authentication
Multi-factor authentication requires a user to present two or more distinct kinds of evidence: something they know, such as a password; something they have, such as a phone or hardware key; or something they are, such as a fingerprint. It reduces the damage when one factor, usually the password, is stolen.
For a spec page, list:
- The factors supported: authenticator app codes, hardware security keys, text messages, email codes.
- Whether MFA is optional, can be enforced by an administrator or is mandatory.
- Whether it applies to SSO sign-ins or is delegated to the identity provider. Many organisations enforce MFA at the identity provider and expect the product to rely on it.
- Recovery options, because a recovery route that is easy to abuse weakens the whole arrangement.
Be careful with text-message codes; they are better than nothing but weaker than app-based or hardware factors, and some organisations disallow them. Listing them honestly lets buyers decide.
Roles and permissions
Beyond signing in, there is the question of what a signed-in user can do. Describe:
- Roles: fixed roles such as owner, admin, editor and viewer.
- Custom roles: whether administrators can define their own.
- Granularity: whether permissions can be set per project, per workspace or per record.
- Audit logs: whether actions are recorded, who can see them, how long they are kept and whether they can be exported.
- Session controls: session duration, forced sign-out and device management.
These items matter to security teams because they show whether the product can follow an organisation's rules about least privilege.
Stating it accurately
Here is a pattern for the access-control block of a fact sheet.
- Single sign-on: supported through SAML 2.0 and OpenID Connect; available on named plans; tested with named identity providers.
- Automatic provisioning: supported through SCIM for create, update and deactivate; group sync not supported.
- Multi-factor authentication: authenticator apps and security keys; administrators can enforce for all users; text messages not supported.
- Roles: four fixed roles; custom roles on named plans.
- Audit log: user actions recorded and retained for a stated period; export available.
- Last reviewed: date.
A claim such as "enterprise-grade access control" has no place in this block.
Common misreadings
"SSO supported" means "SCIM supported". It does not. Check both.
"MFA available" means "MFA enforced". An optional feature that nobody enables protects nobody. Ask whether administrators can require it.
"SAML" means any identity provider will work. Standards leave room for variations. Ask which providers have been tested and whether the vendor will help with setup.
SSO on every plan. Some vendors reserve it for higher tiers. This is a legitimate packaging choice, but it should be stated on the pricing page and the fact sheet, not discovered during procurement.
Questions for buyers to ask
- Which SSO protocols and identity providers are supported?
- Is SSO included in our plan or an add-on?
- Is automatic provisioning available and which operations does it cover?
- Can administrators enforce MFA and disable weaker factors?
- Can we disable password sign-in once SSO is enabled?
- What happens to a user's data when they are deactivated?
- How are actions logged and for how long?
A day in the life: joiner, mover, leaver
The value of these features becomes clear when you follow a single employee through an organisation.
Joiner. A new colleague starts on Monday. Without automation, an administrator must remember to create an account in every product and choose the right role. With SCIM and group mapping, the identity provider creates the account when HR records the hire, places the person in the right groups and the product assigns the matching role. The new colleague signs in with SSO on their first morning and finds the access they need.
Mover. The same person moves from sales to support in the spring. Their group memberships change at the identity provider. With provisioning in place, the product removes the sales role and grants the support role without anyone raising a ticket. Without it, the person quietly accumulates access to everything they have ever needed, which is how over-privileged accounts arise.
Leaver. The person leaves in the autumn. Their identity-provider account is disabled. SSO sign-in stops working at once. If SCIM is configured, the product deactivates the account too; otherwise it sits in the user list, possibly still consuming a seat and possibly still holding a personal access token that bypasses SSO. This last point is worth asking about directly: can tokens and API keys created by a user be revoked automatically when the user is deactivated?
Walk a vendor through this story during evaluation. The answers show quickly whether the features are designed for real administration or merely listed.
Where the line sits between product and identity provider
A frequent source of confusion is who is responsible for what. The identity provider decides how strong authentication is, whether a second factor is needed and what the password rules are. The product decides what an authenticated person may do inside it and how long a session lasts. When specification pages blur this line, buyers cannot tell which controls they will have to configure themselves. Say plainly which settings live in the product and which depend on the identity provider, and link to setup guides for each.
Summary
SSO moves sign-in to an identity provider; SAML and OpenID Connect are the protocols that carry it; SCIM automates account creation and removal; MFA strengthens proof of identity. Each is a separate fact. State which you support, on which plans, with which options, and avoid umbrella phrases. Buyers who find precise answers move faster, and so do the assistants summarising your page.
Questions and answers
- What does single sign-on do?
- It lets people sign in to a product using an account managed by their organisation's identity provider, so access is controlled in one place rather than separately in every tool.
- What is SCIM?
- The System for Cross-domain Identity Management is a standard way for an identity system to create, update and remove user accounts in other products automatically.
- Is SSO the same as multi-factor authentication?
- No. SSO is about where authentication happens. Multi-factor authentication is about requiring more than one kind of proof. The two are commonly combined, with the second factor enforced at the identity provider.
- Why is SSO often listed only on higher plans?
- Vendors often package it with other administration features. A spec page should state plainly which plans include it so buyers are not surprised.