Topic starter
27/08/2026 8:35 am
TL;DR: The “SSO Tax” turns secure login into a licensing surcharge, with some SaaS plans forcing buyers into higher tiers or custom contracts to enable federated access, according to Unixi. The governance issue is that identity controls are being treated as monetised features, which distorts IAM decisions and encourages insecure workarounds.
Editorial analysis by NHI Mgmt Group, based on content published by Unixi: “Breaking Free from the “SSO Tax””.
By the numbers:
- The average enterprise runs over 300 SaaS applications, with 305 cited in Zylo’s 2026 SaaS Management Index.
Key questions
Q: What breaks when Single Sign-On is locked behind a higher SaaS tier?
A: When SSO is priced as an upgrade, organisations often leave apps on local credentials, delay federation, or accept exceptions that weaken identity governance.
Q: Why does charging extra for secure login create security risk?
A: Because it turns a basic authentication control into a commercial decision.
Q: How should IAM teams handle applications that make federation a paid feature?
A: They should treat those apps as governance exceptions, not routine purchases.
Practitioner guidance
- Map SSO as a control requirement Define Single Sign-On support as a mandatory security and governance requirement for applications that handle business data or employee access, then align procurement reviews to that requirement.
- Flag pricing-driven exceptions Identify apps where federation is absent only because the needed tier is too expensive, and record those exceptions as governance risks rather than acceptable cost trade-offs.
- Prioritise shadow SaaS onboarding Bring unmanaged applications into the identity programme first where local login still exists and the SSO gate is delaying standard access oversight.
Bottom line: The SSO tax is a governance problem because it turns a core authentication control into a pricing decision.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
27/08/2026 8:35 am
SSO pricing is now an identity governance issue, not just a procurement issue: when secure login is sold as an upsell, organisations are forced to negotiate access control through commercial packaging. That changes how identity programmes are adopted, delayed, or bypassed. The result is governance distortion, where the cheapest plan can become the least secure operating model.
A few things that frame the scale:
- Across one million observed logins, 1 in 4 were password-based rather than SSO, 2 in 5 were not protected by MFA and 1 in 5 used a weak, breached or reused password.
A question worth separating out:
Q: What is the difference between SSO convenience and identity governance?
A: SSO convenience is about reducing the number of times users type credentials. Identity governance is about controlling who gets access, how that access is approved, how long it lasts, and how it is removed. A programme can have good convenience and still fail governance if lifecycle and entitlement controls are weak.
👉 Read our full editorial: The SSO tax shows how secure login gets priced as leverage