Topic starter
12/06/2026 8:56 pm
TL;DR: Most organisations still buy SaaS through a fragmented process that obscures renewals, licensing, approvals, and duplication, according to Zluri. The governance problem is not just cost control, but identity and access sprawl across the applications, contracts, and stakeholders that procurement now has to reconcile.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “7 Software Procurement Services for Better SaaS Negotiation”.
Key questions
Q: How should security teams govern shadow IT in SaaS environments?
A: Security teams should govern shadow IT by treating it as unmanaged access, not just unsanctioned software.
Q: Why do SaaS buying decisions create access governance risk?
A: SaaS buying decisions create risk because each new application adds identities, permissions, and integrations that must be managed over time.
Q: What breaks when SaaS renewal management is disconnected from usage data?
A: Organisations keep paying for seats that no longer support a business need and preserve access that should have been removed.
Practitioner guidance
- Map procurement to application ownership Create one record that links each SaaS request to the approver, business owner, contract owner and renewal date so no app sits outside governance.
- Review renewals against active usage Require licence and entitlement review before renewal decisions so dormant subscriptions and duplicate tools are identified before money is committed.
- Consolidate overlapping SaaS functions Use feature overlap analysis to retire duplicate tools, reduce redundant identities and simplify offboarding across the SaaS estate.
Bottom line: The article shows that SaaS procurement complexity can obscure app ownership, renewals and approvals, which is where shadow IT begins to harden into governance debt.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
12/06/2026 10:39 pm
Shadow IT in SaaS procurement is a governance visibility failure before it is a buying failure. The article shows that fragmented purchasing leaves procurement, finance and security without a shared inventory of apps, licences and renewal obligations. That means the control gap is not just price negotiation, but the absence of authoritative ownership across the SaaS lifecycle. Practitioners should treat procurement visibility as an identity governance input, not a back-office reporting task.
A few things that frame the scale:
- The average enterprise SaaS platform connects to 42 or more third-party applications through OAuth tokens, API keys, webhooks and automation platforms.
A question worth separating out:
Q: How should security teams implement identity governance in SaaS-heavy environments?
A: Start with a complete inventory of users, service accounts, integrations, and privileged entitlements across all major applications. Then enforce ownership, periodic review, and automatic deprovisioning when accounts become unused or unassigned. The goal is to make access changes traceable and reversible before stale privileges become a security issue.
👉 Read our full editorial: SaaS procurement services show the governance gap in shadow IT
This post was modified 6 days ago by NHI Mgmt Group