Topic starter
12/06/2026 1:17 am
TL;DR: SaaS adoption is making software faster and cheaper to deploy, but Zluri argues that the resulting sprawl also creates shadow IT, duplicate apps, and governance gaps that expose security, compliance, and cost risk. The real control problem is no longer software procurement alone, but who can approve, monitor, and retire access across the expanding app estate.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How SaaS is Powering the Next Big Revolution”.
Key questions
Q: What breaks when SaaS sprawl is not in your identity catalogue?
A: Access reviews, provisioning, and offboarding all become partial controls.
Q: Why does SaaS sprawl create security risk as well as cost pressure?
A: SaaS sprawl increases the number of accounts, roles, permissions, and integrations that must be governed.
Q: What signals show that SaaS governance is not working?
A: Look for delayed offboarding, repeated manual exports, inconsistent access review responses, and inactive accounts that still carry paid licenses.
Practitioner guidance
- Define app ownership for every SaaS tool Assign a named business owner, technical owner, and access approver to every SaaS application so approval and retirement are not ambiguous.
- Map duplicate and unsanctioned apps Create an authoritative inventory that flags duplicate tools, personal trials, and shadow IT so governance can target the highest-friction sprawl first.
- Extend leaver controls into SaaS Ensure offboarding removes user access, shared accounts, and delegated access across all business apps, not just core enterprise systems.
Bottom line: SaaS sprawl changes the problem from software buying into software governance, because every application adds an identity and access lifecycle.
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 no longer just a procurement issue. It is an identity governance issue because every unmanaged app introduces its own access lifecycle, ownership gap, and offboarding risk. The article’s central claim is that software can now be acquired faster than governance can track it. That changes the control model from budget oversight to identity assurance, where approval and retirement matter as much as purchase.
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: How should security teams govern distributed SaaS without slowing the business down?
A: Use a shared operating model. Business units can keep local ownership, but security teams need inventory, approval rules for sensitive settings, and monitoring for integrations and external sharing. That keeps the organisation from turning speed into hidden access sprawl. The goal is not central approval for everything, but visible accountability for anything that changes the trust boundary.
👉 Read our full editorial: SaaS sprawl is turning software governance into an identity problem
This post was modified 4 days ago by NHI Mgmt Group