Notifications
Clear all
Topic starter
12/06/2026 1:17 am
TL;DR: SaaS cost management is presented as a way to control subscription sprawl, right-size licenses, and prevent auto-renewal waste, but Zluri's guide also shows how weak visibility, decentralised buying, and shadow IT create budget and governance risk. The real issue is not just spend reduction, but who has authority over software access and renewal decisions.
NHIMG editorial — based on content published by Zluri: SaaS Management SaaS Cost Management
By the numbers:
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
Questions worth separating out
Q: How should organisations control SaaS spend without losing governance over access?
A: They should treat SaaS spend as part of identity and lifecycle governance, not just procurement.
Q: Why do decentralised SaaS purchases create security and cost risk?
A: Decentralised purchasing breaks the connection between approval, visibility, and renewal.
Q: What breaks when organisations rely on auto-renewals for SaaS subscriptions?
A: Auto-renewals turn a governance decision into a default state.
Practitioner guidance
- Centralise SaaS ownership Create a single inventory that maps each application to a business owner, technical owner, and renewal date.
- Recertify unused seats before renewal Compare assigned licenses with actual usage and flag dormant accounts, duplicate tools, and unused premium features.
- Bring shadow IT into review Detect unsanctioned SaaS by correlating finance records, SSO logs, and browser or endpoint discovery.
What's in the full article
Zluri's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step tactics for centralising SaaS apps and spending across departments
- Specific guidance on monitoring license usage and spotting underused subscriptions
- Procurement and renewal process detail for reducing auto-renewal waste
- Examples of how Zluri maps SaaS apps, categories, and renewal calendars in practice
👉 Read Zluri's guide to SaaS cost management and subscription spend control →
SaaS cost management: what identity teams are missing?
Explore further
12/06/2026 11:05 am
SaaS cost management is an access governance discipline disguised as finance. The article focuses on spend, but its failure modes are classic IAM issues: decentralised buying, missing ownership, and license drift. Once access decisions are distributed without lifecycle controls, cost leakage becomes the visible symptom of governance failure. The practitioner takeaway is that software spend and software authority should be managed together.
A few things that frame the scale:
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to Ultimate Guide to NHIs.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security.
A question worth separating out:
Q: Who should own SaaS license recertification and renewal decisions?
A: Ownership should sit with a named business controller supported by IT, security, and procurement. That owner should confirm usage, validate business need, and approve renewal or removal. If no one owns the decision, the subscription will usually persist by inertia, which is how waste and unmanaged access accumulate.
👉 Read our full editorial: SaaS cost management exposes the governance gap behind sprawl
