Topic starter
11/06/2026 11:34 pm
TL;DR: Disparate IGA models create manual work, visibility gaps, and audit friction because access requests, reviews, provisioning, and SaaS visibility are split across tools, according to Zluri. The governance problem is structural: control quality depends on whether identity data moves as one system or as disconnected fragments.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Disparate Vs Converged IGA Model: What Actually Works”.
Key questions
A: The review process loses a single authoritative entitlement record, so teams must reconcile data manually and may certify against stale or incomplete access state.
Q: When should organisations prioritise a converged IGA model over best-of-breed tools?
A: Prioritise convergence when manual reconciliation, audit prep, or inconsistent access state is becoming routine across provisioning, review, and SaaS visibility.
Q: What are the signs that fragmented IGA is failing in practice?
A: Common signs include repeated exports, cross-tool data mismatches, delayed reviews, and access changes that appear in one system but not another.
Practitioner guidance
- Audit identity-state duplication List every place where provisioning, access review, access request, and SaaS visibility hold separate records, then mark the manual reconciliation steps that keep them aligned.
- Test review evidence coherence Sample recent access certifications and verify that the same entitlement set appears consistently across the source system, the review workflow, and the audit export.
- Measure revocation completeness Check whether access removals in one application are reflected in every connected governance and usage view before you treat revocation as complete.
Bottom line: Fragmented IGA makes control quality depend on manual reconciliation across separate tools, which weakens consistency and visibility.
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 8:18 am
Converged IGA is fundamentally a control-coherence problem, not a feature-count problem. The article shows that fragmented tooling weakens governance because review, request, provisioning, and SaaS visibility no longer move together as one system. When identity state is split across tools, every downstream control depends on manual reconciliation, which creates inconsistent enforcement and avoidable blind spots. Practitioners should judge IGA architecture by whether it preserves a single governance truth.
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 should security teams decide whether to retire legacy IGA tools?
A: Teams should retire legacy tools only after proving that the converged platform preserves the same identity records, review evidence, and revocation outcomes across the lifecycle. If a disconnected system still owns authoritative data for any workflow, retirement will create a governance gap. The question is not whether the old tool is redundant, but whether its state has been safely absorbed.
👉 Read our full editorial: Converged IGA vs disparate tools: what really changes
This post was modified 4 days ago by NHI Mgmt Group