Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How should organisations plan for IGA maintenance after…
Governance, Ownership & Risk

How should organisations plan for IGA maintenance after go-live?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 18, 2026 Domain: Governance, Ownership & Risk

Teams should plan for continuous role updates, policy changes, integration support, and exception handling as permanent workstreams. IGA is not a deployment that ends at go-live. It is an operational control that degrades unless the programme keeps funding data hygiene, review support, and change management.

Why IGA Needs an Operating Model After Go-Live

IGA succeeds or fails on the strength of its day-two operating model. The first live access review, the first policy exception, and the first connector breakage usually expose whether the programme was designed as a sustained control or treated as a project that simply finished on launch day.

At a practical level, maintenance is not just keeping the platform online. It means keeping roles aligned to how the business actually works, keeping entitlement data trustworthy, and keeping ownership clear when applications, teams, or approval paths change. If those inputs drift, the control still exists but its decisions become less reliable.

That is why Identity governance and administration (IGA) platform rollout playbook matters beyond implementation: it frames rollout as a sequence that must preserve governance continuity, testing discipline, and metrics once the platform is live.

What Must Keep Changing After Go-Live?

The most common maintenance workstreams are role management, policy maintenance, connector support, and exception handling. Role models need periodic tuning because business units reorganise, application ownership changes, and accumulated exceptions often signal that the original design no longer matches operational reality.

Policy changes are equally important because access rules do not stay static. New regulatory demands, new joiner-mover-leaver patterns, and new application types can all require updates to approval logic, certification scope, or segregation-of-duties rules. If the policy layer is not maintained, the platform starts reflecting old assumptions rather than current risk.

Connector support is often underestimated because it is not visible to business users until provisioning fails or reviews show stale data. The operational burden includes interface upkeep, attribute mapping corrections, reconciliation checks, and response to source-system changes. Good maintenance also means preserving the quality of the identity data feeding the platform, because review outcomes are only as strong as the records behind them.

For programme teams, the most useful baseline is to treat lifecycle operations as permanent workstreams rather than a backlog. The Joiner-Mover-Leaver (JML) Guide is a useful reminder that lifecycle drift, orphaned access, and delayed deprovisioning are operational issues, not one-time project defects.

What Breaks If Maintenance Is Underfunded?

When maintenance is not funded, IGA degradation usually shows up in three places: review quality, provisioning accuracy, and exception growth. Reviews become noisier, managers rubber-stamp more often, and teams start creating workarounds because the standard process is too slow or too brittle. That turns the control from a governance mechanism into a paperwork exercise.

Underfunded maintenance also creates a hidden resilience problem. Breaks in integration support can stall access requests, delay removals, or leave entitlements unchanged after a role move. Over time, this increases privilege creep and makes it harder to prove that access decisions are still based on current business need.

The maintenance burden is not only technical. It is also organisational. If ownership for roles, connectors, and exception handling is unclear, issues linger because no team sees them as part of its normal remit. The result is a slow accumulation of unmanaged exceptions that eventually becomes harder to unwind than to prevent.

That is why the most relevant operating question is not whether the platform is live, but whether the organisation has a durable process for keeping it current. The Access Reviews and Certification Guide is directly relevant here because review programmes only remain effective when they are closed-loop, risk-aware, and continuously supported.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5CM-3 — Configuration Change ControlIGA maintenance depends on controlled changes to roles, policies and connectors.
IA-5 — Authenticator ManagementIdentity governance relies on ongoing lifecycle control of credentials and related access material.
AC-2 — Account ManagementDay-two IGA work keeps account and entitlement state aligned with business changes.
Recommendation — Apply CM-3 to govern IGA changes through review, approval and traceable implementation. Use IA-5 to manage credential issuance, rotation and revocation tied to IGA processes. Use AC-2 to maintain account lifecycle controls and timely removal of stale access.
CIS Controls v8CIS-5 — Account ManagementIGA maintenance is fundamentally about keeping accounts, roles and access current.
Recommendation — Apply CIS-5 to maintain account inventories and remove access that no longer matches need.
ISO/IEC 27001:2022A.5.15 — Access controlIGA maintenance preserves access control decisions after go-live.
Recommendation — Maintain access control rules and reviews so live governance stays aligned to business need.

Practitioner Guidance

What to prioritise: Put ownership around the highest-churn maintenance items first, especially role changes, entitlement mapping, connector health, and exception governance. Those are the places where live drift usually starts.

What to verify: Confirm that someone is accountable for each of these four things: business role maintenance, technical integration support, policy updates, and review remediation. If any of them is “shared”, the maintenance model is probably too weak to survive steady-state operations.

Decision rule: If a change affects how access is granted, reviewed, or removed, treat it as an IGA change management event, not a one-off support ticket. That keeps the control model current and prevents local workarounds from becoming permanent.

What practitioners underestimate: The biggest long-term cost is usually not licence or infrastructure spend, but the continuous effort required to keep identity data, exceptions, and review logic trustworthy enough for the control to keep working.

Practitioner takeaway: An IGA programme is only truly live when the organisation has funded the routine work needed to keep its governance decisions accurate, explainable, and current.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org