Topic starter
12/06/2026 10:22 pm
TL;DR: Quantum Brilliance cut SaaS costs by 30 to 50 percent and improved offboarding, visibility, and compliance support after replacing spreadsheet-based administration with unified SaaS discovery, license management, access reviews, and automated notifications, according to Josys. The case shows that unmanaged application sprawl is both a financial control problem and an identity governance problem.
Editorial analysis by NHI Mgmt Group, based on content published by Josys: “How Quantum Brilliance Reduced SaaS Costs and Strengthened IT Visibility and Security with Josys”.
By the numbers:
- Quantum Brilliance saw 30–50% SaaS cost reduction through license optimization and eliminating unused subscriptions.
Key questions
Q: What fails when SaaS visibility depends on spreadsheets?
A: Spreadsheet-led SaaS management fails because it cannot continuously reconcile app ownership, active accounts, usage, and offboarding state.
Q: Why do unused SaaS licences create identity risk as well as cost waste?
A: Unused licences often indicate that apps are still licensed after the people or teams that justified them have changed.
Q: What are the signs that employee offboarding is failing in practice?
A: Common warning signs include still-active sessions after termination, lingering logins on SaaS platforms, missed shared credentials, and unexpected file downloads or configuration changes.
Practitioner guidance
- Centralise SaaS inventory and ownership Create one governed view of all SaaS apps, owners, and access paths so decentralised procurement does not outrun control.
- Link license reviews to access reviews Use unused seats and inactive subscriptions as triggers for entitlement review, admin validation, and removal of stale accounts.
- Automate leaver-triggered revocation Connect offboarding events to app-specific notifications and revocation workflows so departures do not rely on manual follow-up.
Bottom line: SaaS sprawl becomes an identity governance problem when teams lose track of ownership, access, and offboarding across a growing application estate.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
13/06/2026 1:05 am
SaaS visibility debt is a governance failure, not an inventory inconvenience. When organisations cannot see their application estate, they cannot reliably govern access, spending, or offboarding across it. The control gap is not just missing data, but missing decision authority over what is active and who still depends on it. The implication is that SaaS discovery has to be treated as identity governance infrastructure, not a back-office reporting task.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should security teams prove SaaS governance for ISO 27001 audits?
A: They should be able to show a current SaaS inventory, access review evidence, revocation timestamps, and reports that tie each control to a specific application owner. Auditors are looking for proof that access is reviewed and removed consistently, not just that a policy exists. If the evidence lives in multiple spreadsheets, the control will be difficult to defend.
👉 Read our full editorial: SaaS visibility gaps turn identity governance into a cost and risk issue
This post was modified 2 days ago by NHI Mgmt Group