Auditors look for evidence that no one person can complete high-risk actions without checks and balances. That includes toxic access combinations, real-time control enforcement, and records showing conflicts were detected and resolved. Teams also need to show that approval workflows prevent conflicting access from being granted in the first place.
What auditors expect to see in SoD evidence
Auditors are not just checking that a policy exists. They want to see that separation is real in day-to-day operations, with conflicting privileges prevented, detected, and remediated across the approval chain. That usually means reviewing role design, access request controls, exception handling, and evidence that high-risk combinations are identified before they can be used.
They will also look for a control narrative that matches the system behaviour. If the process says no one person can create, approve, and execute a sensitive action, the records should show that the workflow enforces that split and that reviewers can prove it with logs, tickets, and access history. Auditors often compare policy intent with actual access pathways, not just written procedures.
In practice, the strongest evidence is specific and traceable: who requested access, who approved it, what conflict was checked, what compensating control was applied, and whether the action was blocked or escalated. For a deeper explanation of how those control patterns are built, see the Segregation of Duties (SoD) Guide.
What counts as a SoD control failure
A separation of duties control fails when a user can combine incompatible responsibilities in a way that removes the intended check and balance. Common examples include a single person being able to request and approve their own access, create and release payments, or move a change from development to production without independent review. Auditors care about both the design flaw and the operational exception path.
They also examine whether the conflict is prevented at the point of grant or merely reviewed later. Preventive controls are stronger than detective ones, but many organisations rely on detective review because business exceptions exist. In that case, the audit question becomes whether the exception is time-bound, approved at the right authority level, and tied to a documented compensating control.
Controls can be weakened by role sprawl, inherited permissions, shared accounts, or workflows that allow admin override without traceable justification. Where role and access design are part of the issue, the relationship between entitlement design and SoD checks is covered well in IAM and IGA Basics and the Core Security Principles Guide.
How auditors judge prevention, monitoring, and remediation
Auditors usually want three things to line up: a defined SoD rule set, enforcement in the workflow or access layer, and evidence that violations are handled consistently. If a toxic access combination is allowed for operational reasons, they look for a documented exception, a risk acceptance owner, and a compensating control that still preserves accountability. If the control only exists on paper, it will not survive review.
Monitoring matters because SoD problems often emerge after role changes, emergency access, or new integrations. A good control environment produces a repeatable record of conflicting access checks, alerts, review outcomes, and removals. That is why access review cadence, entitlement governance, and removal of excess privilege are often part of the same audit story, even when the headline question is only about SoD.
For teams that need to tighten the control design itself, the most relevant implementation pattern is to remove unnecessary privilege before trying to monitor around it. The Least Privilege Techniques Guide shows how to reduce the number of combinations that need to be monitored in the first place. In workflow-heavy environments, the Access Control Policy Template is useful for aligning policy wording with enforceable approval and review requirements.
Risk and Threat Considerations
SoD breaks become dangerous when the same actor can both create a condition and approve the outcome, because that removes independent challenge and makes fraud, abuse, and error harder to catch. The exposure is highest where financial, production, or privileged administrative actions can be executed quickly and leave limited time for after-the-fact correction.
Failure mechanism: A conflicting role, privilege, or approval path allows one person to complete an end-to-end sensitive process without meaningful oversight, or allows an override path that bypasses the intended check.
Impact: The organisation can lose control over high-risk actions, making unauthorized changes, improper payments, fraudulent approvals, and untraceable exceptions more likely and harder to detect.
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 | Directly governs incompatible duty splits and conflict prevention in access control. |
| AC-6 — Least Privilege | SoD audits often examine whether excess privilege creates avoidable duty conflicts. | |
| AU-2 — Event Logging | Auditors need logs that show conflict checks, approvals, overrides, and remediation. | |
| Recommendation — Enforce AC-5 to prevent one person from completing incompatible high-risk actions alone. Apply AC-6 to remove permissions that create unnecessary SoD conflicts. Log approval, override, and conflict-handling events so SoD evidence is traceable. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | SoD is an access-control requirement that must be defined and enforced consistently. |
| Recommendation — Define and enforce access rules that stop conflicting duties from being granted together. | ||
| CIS Controls v8 | CIS-5 — Account Management | Account and entitlement control determines whether conflicting access can be assigned or retained. |
| Recommendation — Review and remove account access that creates conflicting duties or excessive privilege. | ||
Practitioner Guidance
What to verify: Test the workflow, not just the policy. Auditors will expect evidence that the control blocks or escalates a real conflict at the moment access or action is requested, and that the record shows who approved, why, and under what exception basis.
Common mistake: Treating periodic review as a substitute for prevention. A retroactive review may help with detection, but it does not prove the organisation can stop a conflicted user from executing a high-risk action when it matters.
Practitioner takeaway: The strongest SoD posture is one where conflicting access is prevented by design, exceptions are rare and time-bound, and every override leaves a clear audit trail that explains who accepted the risk and why.
Related resources from NHI Mgmt Group
- Why do separation of duties controls fail even when policies exist?
- Why do internal controls need more than separation of duties?
- Why do separation of duties controls fail when RBAC is poorly designed?
- What breaks when separation of duties is not in place for access management and financial controls?
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