Topic starter
12/06/2026 1:19 am
TL;DR: SaaS sprawl, shadow IT, and inefficient joiner-mover-leaver handling make SaaS Operations a governance problem as much as an operational one, according to Zluri. The control gap is that discovery, access review, and offboarding often lag the rate at which applications and accounts are created.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “SaaS Operations (SaaS Ops) - The Complete Guide”.
Key questions
Q: Why do SaaS sprawl and identity governance fail in the same place?
A: They both depend on discovery happening before control.
Q: Why do SaaS sprawl and shadow IT create IAM risk?
A: They create IAM risk because each unmanaged application introduces another identity system, another set of privileges, and another place where access can persist after need changes.
Q: How can teams tell whether SaaS governance is actually working?
A: Look for evidence that discovered applications can be assigned an owner, tied to an access policy, and removed through an enforced workflow.
Practitioner guidance
- Implement authoritative SaaS discovery Build a live inventory of sanctioned and unsanctioned applications, then reconcile it against procurement, SSO, and expense data so access reviews start from reality rather than spreadsheets.
- Automate joiner-mover-leaver workflows for SaaS Connect onboarding, role change, and offboarding steps to app ownership and usage signals so access is granted and revoked consistently across the SaaS estate.
- Review dormant and redundant SaaS licences Use usage telemetry to identify unused, duplicate, or wrong-tier subscriptions, then rightsize the estate before renewals or auto-renewal decisions lock in waste.
Bottom line: SaaS sprawl creates an identity governance gap when discovery, access, and offboarding cannot keep up with application adoption.
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:10 am
SaaS sprawl is an identity governance failure disguised as application growth: The article is describing a control problem, not just an inventory problem. When employees can adopt SaaS faster than governance can discover it, the approved-app catalogue stops being the source of truth. The practitioner conclusion is that SaaS governance has to begin with authoritative discovery, not with policy documents.
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 organisations govern SaaS access when teams can buy apps outside central IT?
A: Treat SaaS governance as an inventory and entitlement problem, not just a login problem. Central IT needs visibility into app ownership, usage, approvals, and direct-admin access so it can identify shadow apps, overprovisioning, and dormant entitlements. Without that control plane, decentralised purchasing turns into decentralised risk.
👉 Read our full editorial: SaaS operations expose the identity governance gap in sprawl
This post was modified 4 days ago by NHI Mgmt Group