Topic starter
12/06/2026 12:08 am
TL;DR: Legacy on-prem IGA systems struggle to keep pace with hybrid work, SaaS sprawl, and modern security expectations, according to Zluri, because integration, scalability, and maintenance burdens create visibility gaps that static deployments were never designed to absorb. The governance problem is not just migration friction, but a control model that lags the identity surface it is meant to govern.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Overcome Legacy Barriers:Modernize Your IGA Now”.
By the numbers:
- Nearly 40% of organizations still have not deployed cloud-based IGA solutions, according to Omada’s State of Governance 2025 report cited by Zluri.
- A company with 500 employees can expect to spend anywhere between $300k to $500k on the implementation process, according to Zluri.
- Zluri says its integration layer includes over 300 prebuilt connectors with popular SaaS and cloud apps.
Key questions
Q: What breaks when legacy IGA is used in cloud-first environments?
A: Legacy IGA breaks down when identity change outpaces manual governance.
Q: Why do legacy IGA tools create more risk for smaller organisations?
A: Legacy IGA often assumes large IT teams, long implementation projects, and custom integrations.
Q: What do teams get wrong when modernising IGA?
A: Many teams focus only on replacing the platform and underestimate the need to redesign access policies, certification cadence, and data sources.
Practitioner guidance
- Map current identity sources and workflow delays Inventory where identities, entitlements, and access requests are stored, then measure provisioning, deprovisioning, and certification cycle times across those systems.
- Prioritise integrations that reduce custom coding Favour IGA options that connect directly to IdPs, HRMS platforms, SaaS applications, and on-prem systems without heavy bespoke scripting.
- Rebuild access policies around zero trust and least privilege Replace static entitlement assumptions with policies that verify access at change points and limit permissions to the minimum needed for current tasks.
Bottom line: Legacy on-prem IGA can still operate, but it struggles to govern modern hybrid environments with enough speed and visibility to stay reliable.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 9:11 am
Legacy IGA is now a visibility control problem, not just a deployment problem. The article shows that on-prem governance breaks down when identity data, SaaS entitlements, and workflow triggers are scattered across too many systems for a static control plane to reconcile quickly. That creates blind spots in certification, access updates, and exception handling. The practitioner conclusion is straightforward: if governance cannot see current access, it cannot credibly govern it.
A few things that frame the scale:
- Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.
A question worth separating out:
Q: How do organisations know whether their IGA programme is actually working?
A: Look for fewer orphaned accounts, fewer unresolved SoD conflicts, and a lower rate of redundant approvals in certification campaigns. If the programme is healthy, access reviews should produce cleaner entitlement data and fewer exceptions over time, not just higher completion percentages.
👉 Read our full editorial: Legacy on-prem IGA creates visibility and scalability gaps
This post was modified 4 days ago by NHI Mgmt Group