Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

SaaS sprawl and abandoned apps: what IAM teams are missing


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 9079
Topic starter  

TL;DR: Rising SaaS spend and unmanaged app usage create hidden costs and governance gaps as organisations lose visibility into licenses, renewals, duplicate tools, and abandoned access, according to Zluri and Gartner. The identity problem is not just overspend: app lifecycle control across people, subscriptions, and access ownership is now a security requirement.

NHIMG editorial — based on content published by Zluri: Vendor Management How CFOs can Leverage SMPs to Optimize SaaS Spending?

By the numbers:

Questions worth separating out

Q: How should teams reduce SaaS overspend without losing control of access?

A: Start with a reconciled inventory of subscriptions, active users, and business owners.

Q: Why do abandoned SaaS apps create both cost and security risk?

A: Abandoned apps keep consuming budget through renewals while their linked accounts, permissions, and data access may remain active.

Q: What do security teams get wrong about duplicate SaaS tools?

A: They often treat duplicates as a finance issue and ignore the identity impact.

Practitioner guidance

  • Reconcile licenses against live accounts Build a monthly process that compares purchased subscriptions with active users, recent usage, and business owner confirmation so unused licenses can be removed before renewal.
  • Assign an owner to every SaaS application Require a named business and IT owner for each app so renewal, access review, and termination decisions have a clear accountable party.
  • Link offboarding to subscription termination Make app retirement part of employee exit and project closure workflows so abandoned accounts, linked data access, and renewals are closed together.

What's in the full article

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

  • Concrete examples of how the SaaS management platform surfaces unused licenses and duplicate applications.
  • The article's walkthrough of renewal calendar and contract visibility for month-by-month spending oversight.
  • Practical examples of downgrading subscriptions to lower tiers based on actual app usage patterns.
  • The offboarding scenario showing how abandoned apps can keep renewing after an employee leaves.

👉 Read Zluri's analysis of SaaS spending controls for CFOs and IT teams →

SaaS sprawl and abandoned apps: what IAM teams are missing?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 2 months ago
Posts: 8508
 

App abandonment is an identity lifecycle failure, not a procurement oversight. The article shows that subscriptions continue after employees leave or projects end because ownership and offboarding are not joined up. That creates a governance gap where access, payment, and accountability all outlive the business need. The practitioner lesson is to treat abandoned SaaS as a lifecycle control defect.

A few things that frame the scale:

A question worth separating out:

Q: Who should own SaaS renewal and offboarding decisions?

A: Renewal and offboarding should be jointly owned by the business app owner, IT, and security or identity governance teams. That prevents subscriptions from auto-renewing after use has ended and ensures the access, contract, and retirement decisions happen through one accountable workflow.

👉 Read our full editorial: SaaS spend management exposes the hidden identity governance gap



   
ReplyQuote
Share: