Topic starter
12/06/2026 12:04 am
TL;DR: Traditional identity governance still leaves many enterprises with poor visibility, slow deployment cycles, and identity debt as cloud, legacy, OT, and AI-connected environments expand, according to Gathid’s analysis. The real shift is from one-time implementation to continuous, contextual governance across the full identity estate.
Editorial analysis by NHI Mgmt Group, based on content published by Gathid: “The IAM Reality Check: Why Most Organizations Are Stuck”.
By the numbers:
- Full IGA can take 12 to 24 months to reach phase one of deployment, according to Gathid.
Key questions
Q: When does light IGA stop being enough for an identity programme?
A: Light IGA stops being enough when the environment includes conflicting sources of truth, segregation-of-duties enforcement, toxic access checks, legacy applications, or OT systems that require deeper policy reconciliation.
Q: Why does identity debt keep growing even after governance tools are deployed?
A: Identity debt grows because access changes continuously while many governance programmes still operate on project timelines.
Q: How should organisations decide between Light IGA and Full IGA?
A: They should decide based on governance scope, not feature labels.
Practitioner guidance
- Implement continuous access observability Track entitlement changes as they happen across cloud, legacy, OT, and SaaS environments so governance decisions are based on current state, not last quarter's export.
- Segment governance by use case depth Use light IGA for straightforward provisioning and access reviews, but reserve full governance workflows for SoD, toxic access checks, and multiple-source reconciliation.
- Measure identity debt as a live risk Create metrics for stale entitlements, overdue deprovisioning, and unresolved access exceptions so the backlog is visible before it becomes operational debt.
Bottom line: Identity governance fails when it is treated as a one-time implementation rather than a daily control process.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
12/06/2026 9:05 am
Identity governance has crossed from implementation problem to operating model problem. The article is right to move the discussion away from buying a platform and toward embedding governance into daily work. That shift matters because the main failure mode is no longer feature coverage alone, but the delay between identity change and governance response. Practitioners should treat continuous observability as the baseline assumption for modern IGA.
A question worth separating out:
Q: How should organisations decide between Light IGA and Full IGA?
A: They should decide based on governance scope, not feature labels. If the environment needs entitlement catalogues, role engineering, segregation of duties enforcement, or coverage across disconnected systems, lightweight governance will not be enough. If the estate is simple, cloud-connected, and already visible, Light IGA may cover the immediate need while a fuller roadmap is built.
👉 Read our full editorial: Identity governance is shifting from projects to daily practice
This post was modified 1 day ago by NHI Mgmt Group