Topic starter
06/07/2026 9:47 am
TL;DR: Integration depth, automated maintenance, and direct provisioning are what let identity programmes keep pace with hundreds of apps across hybrid environments, because connectivity has become the critical failure point in IGA, according to Lumos. The real lesson is that access sprawl is now a control-plane problem, not an exception-handling problem.
Editorial analysis by NHI Mgmt Group, based on content published by Lumos: “How We Use AI to Build Integrations at Lumos”.
Key questions
Q: What breaks when IGA does not cover the full application estate?
A: When IGA does not cover the full application estate, joiner, mover, leaver processes fall back to manual handling, access reviews become inconsistent, and audit evidence fragments across local owners and ticket queues.
Q: Why do incomplete integrations create risk even when access policies are well defined?
A: Because policy only matters when the platform can enforce it in the systems where access actually exists.
Q: How should security teams evaluate an IGA platform for hybrid environments?
A: They should test whether the platform can reconcile identities, entitlements, approvals, and lifecycle events across cloud, SaaS, and on-prem systems.
Practitioner guidance
- Map governance coverage against the full application estate Inventory which applications are actually connected for provisioning, entitlement discovery, and access reviews, then separate compliant coverage from manual exception handling.
- Assess connector fidelity before enabling direct provisioning Verify that each connector can accurately reflect accounts, entitlements, permission sets, and custom actions in the target system before expanding automation.
- Make integration maintenance part of control ownership Assign explicit ownership for testing, updating, and revalidating connectors when application APIs, schemas, or permission models change.
Bottom line: Identity governance fails when integrations cover only a narrow slice of the application estate and the rest of access falls back to manual handling.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/07/2026 10:03 am
The control-plane gap is now the central IGA problem. Identity programmes fail less often because of policy theory than because the platform cannot operationalise that policy across enough applications. When integration coverage stops at a handful of critical systems, the rest of the estate moves into manual exception handling, and governance becomes partial by design. The practitioner conclusion is blunt: incomplete connectivity is a governance failure, not just a deployment backlog.
A question worth separating out:
Q: Should organisations prioritise more integrations or deeper governance workflows first?
A: Deeper workflows only help after the platform can reach the systems that matter. For most teams, integration coverage comes first because a sophisticated workflow that touches a narrow slice of the estate leaves the majority of access outside governance.
👉 Read our full editorial: Autonomous identity integrations expose the IGA control plane gap