Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Transition Matrix
Governance, Ownership & Risk

Transition Matrix

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

A transition matrix is a control document that defines which governance system is authoritative for each workflow during coexistence. It prevents ambiguity when legacy and new IGA platforms overlap. The matrix should cover requests, provisioning, reviews, lifecycle actions, and reporting so that changes do not conflict or duplicate each other.

What a transition matrix does

A transition matrix is the coexistence rulebook for a changeover period. It answers a simple but high-stakes question, which system is authoritative for each workflow while old and new governance platforms overlap. That clarity prevents duplicate actions, conflicting approvals, and gaps in ownership while both systems remain in play.

Its value is not in describing the target state, but in removing uncertainty during migration. When teams know which platform owns a request, a review, or a lifecycle event, they can run parallel environments without creating inconsistent records or competing control decisions.

Why coexistence needs an authority map

Coexistence periods are fragile because the same identity or workflow may be visible in more than one system. Without an explicit authority map, one platform may approve access while another records a different outcome, or both may try to execute the same action. The transition matrix prevents that ambiguity by assigning a single source of truth per workflow.

This makes it especially useful when organisations are moving between legacy and new IGA tooling, where provisioning logic, certification ownership, and reporting paths often do not change on the same schedule. The matrix lets teams decouple the migration of data, users, and processes from the question of who governs each action.

Workflows the matrix should cover

A useful matrix is workflow-specific, not just system-specific. It should identify which platform owns requests, provisioning, access reviews, lifecycle changes, exceptions, and reporting, because each of those controls can fail differently during overlap.

  • Requests, so approvals are not captured twice or lost between systems.
  • Provisioning, so account and entitlement changes are executed once by the right platform.
  • Reviews, so recertification evidence is assigned to the authoritative governance system.
  • Lifecycle actions, so joiner, mover, and leaver events do not trigger conflicting automation.
  • Reporting, so control metrics and audit evidence are sourced consistently.

The best matrices also note handoff conditions, for example when a workflow moves from the legacy platform to the new one, or when a report must be consolidated across both systems for a defined period.

How to use it without creating dual control failure

The transition matrix is most effective when it is treated as an operational control document, not a one-time migration note. It should be versioned, approved, and kept aligned to the actual cutover plan so teams do not rely on outdated ownership assumptions.

It also needs to be precise about exceptions. If a workflow is shared, the matrix should say which system initiates the action, which one records the final state, and how conflicts are resolved. That discipline reduces the risk that legacy automation keeps firing after the new platform is live.

Risk and Threat Considerations

A weak or stale transition matrix creates a control gap during coexistence. The main risk is not just operational confusion, but conflicting authoritative decisions, duplicate provisioning, missed revocations, and reporting evidence that no longer matches the real state.

Failure mechanism: During overlap, two systems can both believe they own the same workflow. That can produce duplicate actions, inconsistent records, or automation loops, especially where request, provisioning, and lifecycle logic are split across platforms.

Impact: The result can be incorrect access outcomes, broken audit trails, delayed remediation, and governance blind spots that persist until cutover is complete and the overlap is retired.

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 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5CM-3 — Configuration Change ControlTransition matrices govern controlled workflow ownership during system changeover.
CM-4 — Impact AnalysesCoexistence planning requires assessing how overlapping platforms affect governance outcomes.
PM-9 — Risk Management StrategyThe matrix is a migration control that reduces operational and governance risk during transition.
Recommendation — Define and approve workflow ownership changes before cutover to prevent conflicting control actions. Analyze overlap impacts so legacy and new systems do not issue conflicting workflow decisions. Use a documented strategy to manage coexistence risk until the old platform is fully retired.
ISO/IEC 27001:2022A.8.32 — Change managementThe term describes controlled transition governance while systems change over.
A.5.37 — Documented operating proceduresThe matrix is an operating procedure that defines authoritative handling across systems.
Recommendation — Control workflow ownership changes through formal change management during migration. Maintain documented procedures that specify which platform owns each workflow.

Practitioner Guidance

Governance implication: Assign one accountable owner for the matrix and keep it synchronized with migration milestones. The matrix should be reviewed whenever workflow ownership, platform scope, or reporting responsibilities change, because stale authority maps are a common source of overlap failures.

What to watch for: Pay close attention to workflows that are easy to overlook, such as exception handling, recertification evidence, and downstream reporting. Those are often where two systems silently diverge, even when the core provisioning path appears stable.

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 October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org