SaaS sprawl and renewal risk: what IAM teams need to know

TL;DR: Rising SaaS spend, weak app visibility, and manual renewal tracking are making financial planning and analysis harder while increasing security and compliance exposure, according to Zluri and Gartner data. The governance problem is no longer budget tracking alone: unmanaged SaaS creates shadow access, unused licenses, and control gaps that identity teams must help close.

NHIMG editorial — based on content published by Zluri: SaaS Management SaaS Challenges that Affect Financial Planning and Analysis

By the numbers:

• According to Gartner's report, cloud software spending increased by 23% in 2021, from $270 billion to $330 billion.

Questions worth separating out

Q: How should teams govern SaaS sprawl without losing budget control?

A: Start with a shared inventory that merges finance, SSO, and application discovery data.

Q: Why does SaaS renewal management matter to IAM teams?

A: Because renewals often preserve active accounts, licences, and permissions even when the business case has ended.

Q: What breaks when SaaS apps are managed manually?

A: Manual tracking produces stale data, missed renewals, and inconsistent ownership records.

Practitioner guidance

• Build a single SaaS inventory from identity and finance sources Combine SSO, expense, and direct application discovery into one inventory so renewals and access reviews use the same authoritative record.
• Tie renewal reviews to entitlement and usage evidence Require app owners to prove active use, named ownership, and access necessity before auto-renewal is approved or deferred.
• Include abandoned SaaS in access review cycles Treat dormant subscriptions and unused licences as governance issues, then reconcile them during quarterly entitlement reviews and offboarding.

What's in the full article

Zluri's full article covers the operational detail this post intentionally leaves for the source:

• How its SaaS discovery methods correlate applications with SSO, finance, API, desktop-agent, and browser-extension signals.
• How renewal alerts are configured for contracts and payments, including the timing logic behind reminders.
• How the platform surfaces app usage, duplicate licences, and abandoned applications for budgeting decisions.
• How visibility data is used to support cost optimisation and risk review across the SaaS stack.

👉 Read Zluri's analysis of SaaS challenges affecting FP&A →

SaaS sprawl and renewal risk: what IAM teams need to know?

Explore further

View Full Forum →  |  NHI Foundation Course →