Topic starter
12/06/2026 1:17 am
TL;DR: SaaS cost optimisation starts with visibility, because duplicate apps, forgotten auto-renewals, and over-tiered licences quietly drain budget and create unmanaged access paths, according to Zluri. The governance lesson is that spend control and identity control are now the same operating problem, especially where unsanctioned apps sit outside IT review.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “5 Ways for SaaS Cost Optimization During Recession”.
Key questions
Q: How should security teams govern access across SaaS sprawl?
A: Security teams should govern SaaS sprawl with one inventory, one policy model, and one review process that covers both human and non-human access.
Q: Why do auto-renewing SaaS subscriptions create access risk?
A: Because renewal extends a service without a fresh decision about who should still have access.
Q: What are the signs that SaaS licence rightsizing is failing?
A: Common signs include premium tiers with low feature use, multiple apps serving the same function, and subscriptions that renew without owner review.
Practitioner guidance
- Build a central SaaS inventory Aggregate SSO, API, finance, browser, and endpoint signals into one authoritative application list so teams can see sanctioned and unsanctioned use together.
- Review every renewal against actual usage Require app owners to confirm active usage, business need, and renewal approval before subscriptions roll over automatically.
- Eliminate duplicate applications by function Group apps by shared business capability, assign an owner for each capability, and retire tools that duplicate an approved service.
Bottom line: SaaS sprawl creates both financial waste and hidden access exposure when apps are bought, renewed, and retained outside a governed inventory.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 11:06 am
SaaS sprawl is an identity governance problem before it is a procurement problem. The article shows that buying, renewing, and downgrading software all depend on knowing who can access what and whether that access is still justified. Once app ownership fragments across departments, licence control and access control stop being separate disciplines. The practical conclusion is that SaaS inventory must be governed as part of the identity programme, not as a finance side task.
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: What should organisations do when employees buy SaaS outside IT review?
A: Decide whether the subscription should be sanctioned, replaced, or revoked, and make that decision part of the procurement and access lifecycle. If employees can buy tools independently and keep using them, the organisation needs a formal intake process so unauthorised software does not become unmanaged access.
👉 Read our full editorial: SaaS sprawl creates cost waste and hidden access risk
This post was modified 4 days ago by NHI Mgmt Group