Topic starter
12/06/2026 12:59 am
TL;DR: Automated SaaS discovery, onboarding and offboarding, renewal controls, and license management reduce shadow IT, wasted spend, and access risk for IT teams, according to Zluri. The governance takeaway is that visibility and lifecycle control matter more than point fixes when SaaS sprawl and delegated access keep expanding, while its own example highlights 225,000 apps in the discovery library and idle software costs of $259 per desktop.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How Zluri Saves Time and Money for IT Teams”.
By the numbers:
- Zluri says the typical cost of idle software is $259 per desktop.
Key questions
Q: What breaks when SaaS discovery finds apps but no one owns them?
A: Discovery without ownership breaks governance because the organisation can identify an application but cannot prove who approved it, who should review it, or who is responsible for offboarding.
Q: Why do hidden SaaS renewals create security risk as well as cost waste?
A: Hidden renewals keep software and its access paths alive after the original business need may have ended.
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 multi-source SaaS discovery Combine identity provider, expense, directory, endpoint, browser, and direct app signals so new SaaS use is visible early.
- Automate SaaS offboarding playbooks Make deprovisioning part of the leaver process so access removal, data backup, and ownership reassignment happen together instead of relying on manual follow-up.
- Attach ownership to every business app Require named app owners before an application can be renewed, approved, or exception-handled.
Bottom line: SaaS governance breaks down when discovery, ownership, renewal, and offboarding are handled as separate tasks rather than one lifecycle.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/06/2026 10:36 am
SaaS governance fails when discovery, access, and cost control are treated as separate problems. Shadow IT is not just an inventory issue. It is a lifecycle problem in which applications enter the estate faster than governance processes can approve, assign, renew, and retire them. The practitioner lesson is that the control plane has to follow the app from first sight to final removal.
A question worth separating out:
Q: Should IAM teams prioritise SaaS lifecycle control over point fixes?
A: Yes, when SaaS sprawl is the dominant problem. Point fixes can reduce friction in a single app, but they do not solve the larger issue of discovery, ownership, renewal, and offboarding across the portfolio. Lifecycle control is the only approach that scales with ongoing application growth.
👉 Read our full editorial: SaaS governance automation changes how IT teams control shadow IT