A conflict matrix is a working list of permissions or roles that must not coexist within the same identity. It is used by IAM and IGA teams to detect and block risky combinations during provisioning, recertification, and access change events.
How a conflict matrix works
A conflict matrix is a control list, not a policy statement. It defines the combinations of permissions, roles, or access paths that must never land in the same identity, so provisioning and review workflows can block them before they create a segregation-of-duties problem.
Its value is in turning governance intent into a deterministic check. Instead of asking reviewers to reason from memory each time, the matrix gives IAM and IGA systems a reusable decision set for high-risk combinations that should be prevented, flagged, or escalated.
Where conflict matrices are used
Conflict matrices usually sit inside identity governance, role engineering, and access request workflows. They are most useful when role design is broad enough that one person could inherit incompatible duties through multiple assignments, indirect entitlements, or inherited group membership.
They also matter during recertification, when an identity may already carry a risky mix of access that was assembled over time. In that case the matrix acts as a screen for dormant conflict, not just a front-door provisioning check.
Because the matrix is evaluated against the identity’s effective access, it needs to account for aggregation across applications, platforms, and delegated administration paths. A narrow view of a single role often misses the actual combination that creates the conflict.
Why conflict matrices matter
The core purpose is segregation of duties. A conflict matrix helps stop one identity from gaining the ability to create, approve, and reconcile the same business event, or to combine access that should be independently controlled for fraud, error, or abuse prevention.
That makes the matrix a governance safeguard as much as a technical one. It reduces the chance that access design drifts into a structure where review is formally completed but materially ineffective because the same person can still perform incompatible actions.
When maintained well, it also improves role hygiene. Teams can use the matrix to spot patterns where users are repeatedly assigned exceptions, which often signals that a role model is too coarse or that business process ownership is unclear.
Common design and maintenance issues
Conflict matrices fail when they are too generic, too stale, or too disconnected from real entitlements. If the matrix only names abstract job functions but not the permissions that actually drive risk, it will miss conflicts that emerge from combinations across systems.
They also become unreliable when exception handling is informal. A one-off approval that is never documented can quietly become a permanent access pattern, which defeats the purpose of the matrix and makes later recertification much harder to trust.
Another common issue is scope drift. As new applications, shared services, and privileged functions are added, the matrix must be updated to reflect the current access model. A conflict list that does not keep pace with the role catalog quickly becomes a historical artifact rather than a control.
Risk and Threat Considerations
Conflict matrices reduce exposure to toxic combinations of access, but they only work if they are accurate, current, and enforced in the provisioning path. If they are incomplete or bypassable, an identity can accumulate mutually incompatible permissions that enable fraud, concealment, or unauthorized override.
Failure mechanism: A weak matrix misses a conflicting role pair, or an exception path bypasses the check, allowing the same identity to gain access that should have remained separated.
Impact: The result can be fraudulent approval chains, undetected transactions, audit failure, and a broader loss of trust in access governance and recertification outcomes.
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.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-5 — Separation of Duties | Conflict matrices operationalize separation-of-duties rules for incompatible access combinations. |
| AC-6 — Least Privilege | Conflict matrices help prevent privilege combinations that exceed necessary access for a single identity. | |
| IA-5 — Authenticator Management | Conflicting access often becomes dangerous when credentials and account lifecycle controls are weakly governed. | |
| Recommendation — Map toxic combinations to AC-5 and block or escalate conflicting access before it is provisioned. Use AC-6 to trim overlapping entitlements that create avoidable conflict exposure. Apply IA-5 to keep account and credential changes aligned with enforced access separation. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Conflict matrices are a practical access-control mechanism for governing incompatible permissions. |
| A.5.18 — Access rights | The matrix governs which access rights may be combined within one identity. | |
| Recommendation — Define and enforce access-control rules that prevent incompatible permissions from coexisting. Review access rights for incompatible combinations before approval and during periodic recertification. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Conflict matrices are used to govern who can hold which permissions together. |
| Recommendation — Use CIS-6 to enforce role separation and reject conflicting access assignments. | ||
Practitioner Guidance
Governance implication: Treat the conflict matrix as a living control owned by both IAM and business control owners, not as a one-time role design artifact. Its entries should reflect the actual combinations that create business risk, including indirect entitlements and inherited access.
What to watch for: Review repeated exceptions, overlapping admin paths, and access reviews that keep passing the same identity despite obviously incompatible duties. Those patterns usually indicate either a flawed role model or a control that is not being enforced where decisions are made.
Related resources from NHI Mgmt Group
- How should organisations build a segregation of duties matrix for modern IAM programs?
- Who is accountable when a SoD conflict leads to fraud or compliance failure?
- Who is accountable when an SoD conflict is missed in an audit or incident?
- What should organisations do when mobile device management and identity policy conflict?
Deepen Your Knowledge
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.
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