TL;DR: ITAM gaps let shadow SaaS, weak access oversight, and poor renewal discipline create security, compliance, and cost risk as organisations scale, according to Zluri. The underlying issue is not tool shortage but governance drift across discovery, access, and lifecycle control.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Top 4 ITAM Challenges And Solutions to Overcome Them”.
By the numbers:
- Zluri says it directly integrates with 300+ apps.
- Zluri says contract alerts can arrive 30 days, 15 days, 7 days, and 1 day before renewal.
Key questions
Q: What breaks when SaaS discovery is incomplete?
A: Incomplete discovery leaves shadow apps, duplicate subscriptions, and employee-purchased tools outside the control model.
Q: Why does fragmented SaaS management create security and operational risk for growing organisations?
A: Fragmented SaaS management creates risk because usage, licenses, and permissions become scattered across tools and teams.
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
- Tighten SaaS discovery inputs Reconcile identity provider data, finance records, direct integrations, and endpoint signals into one owned inventory so shadow apps do not evade review.
- Link app ownership to lifecycle events Assign clear business and IT ownership for each application, then trigger review and revocation actions when users change role or leave.
- Separate renewal approval from auto-renewal Require documented usage evidence and security review before extending contracts, especially for applications with low activity or duplicate function.
Bottom line: Incomplete SaaS visibility turns ITAM into a governance problem because security, compliance, and spend controls all depend on the same inventory.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Incomplete SaaS visibility is a governance failure, not an inventory inconvenience. If the organisation cannot see which applications exist, every downstream control becomes probabilistic. Discovery, ownership, access review, and renewal all depend on the same incomplete picture, so the programme is already operating with blind spots. The practitioner conclusion is that SaaS visibility must be treated as a control dependency, not a reporting nicety.
A few things that frame the scale:
- Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.
A question worth separating out:
Q: Why do SaaS renewals matter to IAM and access governance?
A: SaaS renewals matter because subscription continuation often keeps access alive even when business need has ended. If renewal, ownership, and offboarding are separate processes, organisations end up paying for software that still has active access paths attached. IAM teams should treat renewal timing as part of entitlement governance, not just procurement administration.
👉 Read our full editorial: IT asset visibility gaps are still driving SaaS risk