Notifications
Clear all
Topic starter
12/06/2026 12:48 am
TL;DR: Collaboration between CIOs and CFOs can improve technology investment decisions, reduce SaaS sprawl, and strengthen risk oversight by combining financial and technical perspectives, according to Zluri. For IAM teams, the real issue is governance coherence: access, spend, and control decisions break down when business and technology owners work from separate views.
NHIMG editorial — based on content published by Zluri: Vendor Management CIO CFO Collaboration - An Essential to SaaS Spend Management
Questions worth separating out
Q: How should teams align SaaS procurement with access governance?
A: Treat procurement as the start of the control chain, not the end.
Q: Why does SaaS sprawl create security risk as well as cost pressure?
A: SaaS sprawl increases the number of accounts, roles, permissions, and integrations that must be governed.
Q: What do security teams get wrong about budget transparency?
A: They often treat spend reporting as proof of control maturity.
Practitioner guidance
- Unify application ownership records Build a single inventory that ties each SaaS application to a business owner, a technical owner, a cost centre, and an access review owner.
- Tie approvals to entitlement review Require every new SaaS approval to include the current access model, the intended user population, and the offboarding path.
- Use spend anomalies as governance signals Investigate applications with rising costs, low usage, or repeated renewal exceptions as candidates for access review and rationalisation.
What's in the full article
Zluri's full blog covers the operational detail this post intentionally leaves for the source:
- Examples of how CIO and CFO collaboration changes SaaS renewal and consolidation decisions in practice
- Zluri's dashboard workflow for identifying underutilised, redundant, and non-compliant SaaS applications
- How approval workflows and role-based access control support budget and compliance policy enforcement
- Detailed reporting examples that show how SaaS spend trends can inform future portfolio decisions
👉 Read Zluri's analysis of CIO and CFO collaboration for SaaS spend management →
SaaS spend governance: what CIO and CFO alignment changes?
Explore further
12/06/2026 10:17 am
SaaS governance fails first when ownership is split between buying power and access authority. The article shows that cost oversight and technical oversight are often treated as separate disciplines, but SaaS control only works when both sides share the same decision record. Without that, organisations can approve spend without knowing who can still access the application, or retain software without knowing whether it remains in operational use. The implication is that SaaS governance should be treated as an identity and lifecycle control problem, not a budgeting exercise.
A few things that frame the scale:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which shows how often identity governance lags behind operational reality.
A question worth separating out:
Q: How do organisations know when to retire a SaaS application?
A: Retirement decisions should combine cost, usage, access, and business ownership. If a tool is lightly used, duplicates another capability, or lacks a clear lifecycle owner, it should enter rationalisation review. The key is to remove access and subscriptions together so dormant software does not remain a hidden control gap.
👉 Read our full editorial: CIO and CFO collaboration shapes SaaS spend governance
