Topic starter
12/06/2026 9:32 pm
TL;DR: SaaS spend optimization is presented as a way to cut waste, but the deeper issue is that unused apps, hidden subscriptions, and weak decommissioning also create identity and access exposure, according to Zluri. For IAM and NHI teams, cost control and governance now overlap in the same control surface.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “SaaS Spend Optimization: A Comprehensive Guide”.
Key questions
Q: What breaks when SaaS subscriptions are not tied to access reviews?
A: Orphaned subscriptions and stale entitlements start to accumulate because no one revalidates whether the access still matches the job.
Q: Why does SaaS tail spend create identity risk as well as cost risk?
A: Because every unmanaged subscription can introduce human accounts, admin roles, API access, and vendor support entitlements that are never recertified or removed.
Q: How should organisations decommission SaaS without leaving residual access behind?
A: They should treat every retirement as an access closure event.
Practitioner guidance
- Map SaaS spend to access paths Reconcile every material subscription with the identities, roles, and tokens that can still authenticate to it.
- Tie offboarding to app retirement Require that canceling a SaaS subscription also revokes user access, administrator roles, API keys, and any delegated access created for integrations.
- Review hidden apps before renewal Use discovery data from finance, SSO, directory, and endpoint sources to identify subscriptions that were never formally approved but still carry live access.
Bottom line: SaaS spend optimisation is not just a finance exercise because dormant subscriptions can preserve live access paths and create governance blind spots.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
12/06/2026 11:40 pm
Spend governance and identity governance are converging on the same SaaS control surface. The article is framed as cost optimisation, but the operational reality is that application rationalisation, licence right-sizing, and decommissioning all affect who can still access what. That makes SaaS portfolio management part of identity governance, not a separate finance exercise. Practitioners should treat every app decision as both a budget decision and an access decision.
A few things that frame the scale:
- The average enterprise SaaS platform connects to 42 or more third-party applications through OAuth tokens, API keys, webhooks and automation platforms.
A question worth separating out:
Q: When should finance and identity teams prioritise SaaS rationalisation over simple licence trimming?
A: Whenever unused apps or duplicate tools suggest that the problem is structural, not just seat count. Licence trimming lowers spend, but rationalisation is needed when the real issue is unmanaged access, hidden subscriptions, or failed offboarding.
👉 Read our full editorial: SaaS spend optimization exposes hidden identity and access risk
This post was modified 6 days ago by NHI Mgmt Group