Segregation of duties is a specific internal control that divides responsibility across different people, while internal controls is the broader system of policies, checks, approvals, reconciliations, and monitoring used to manage risk. SoD focuses on preventing one person from controlling a process alone. Internal controls also include detection, governance, and remediation mechanisms.
How SoD differs from the broader internal control system
Segregation of duties is a design rule: no single person should be able to initiate, approve, execute, and conceal the same high-risk activity end to end. General internal controls are the full control environment around that activity, which can include approvals, reconciliations, monitoring, exception handling, logging, and remediation. SoD is one control pattern inside that wider system, not a substitute for it.
That distinction matters because a process can have strong internal controls and still fail if one role can bypass every step, just as strict SoD can still leave gaps if there is no monitoring or reconciliation. In practice, SoD is about separating power; internal controls are about governing the whole process.
Segregation of Duties (SoD) Guide is the right starting point when you need to define toxic combinations, mitigating controls, and where SoD should apply across people, bots, and AI agents.
Why internal controls are broader than SoD
Internal controls cover the full lifecycle of risk management around a process. They can be preventive, detective, or corrective, and they often work together. For example, an approval control may stop an unsafe action, a reconciliation may detect an error after the fact, and a remediation workflow may fix the root cause. SoD only addresses one part of that picture, namely who is allowed to perform each step.
Because of that, SoD is usually evaluated as a specific control objective, while internal controls are assessed as the overall control architecture. A finance process, for instance, may use SoD to keep request, approval, payment, and review in separate hands, but it still needs account reconciliations, audit trails, exception review, and management oversight to manage the full risk.
Core Security Principles Guide helps place SoD in the wider context of least privilege, complete mediation, and secure defaults, which are the design ideas behind many internal controls.
COSO for Cybersecurity Guide is useful when you want to understand how internal controls fit into a broader control framework rather than treating SoD as the whole answer.
What practitioners should look for when distinguishing the two
SoD answers a narrow question: can one person, account, or role complete a sensitive process alone? Internal controls answer a broader question: does the organisation have enough preventive, detective, and corrective mechanisms to keep the process reliable and defensible? That means SoD can exist without strong broader governance, and broader governance can exist without clean SoD if other controls compensate, though the latter usually carries more residual risk.
In audits and control design, the practical test is whether the issue is a role conflict or a process weakness. A role conflict points to SoD. A missing review, weak reconciliation, poor logging, or unclear escalation path points to internal control design more generally. Many real failures involve both: a role conflict creates exposure, then weak monitoring lets it persist.
Top 10 Identity Audit Findings is helpful for seeing how SoD conflicts, access reviews, and missing evidence show up as audit findings in practice.
SOX IT General Controls (ITGC) Guide is a practical reference when SoD is being tested alongside access, change, and evidence controls in a regulated environment.
Change Management Policy Template shows how approvals, emergency changes, and review steps fit together as internal controls, with SoD as only one part of the design.
Risk and Threat Considerations
The main risk in confusing SoD with internal controls is under-controlling the process. If teams believe “we have SoD” and stop there, they may miss monitoring, reconciliation, and remediation controls that catch collusion, error, or policy drift. The opposite mistake also happens: organisations layer many controls around a process but leave one role able to act unchecked, creating a single point of failure and abuse.
Failure mechanism: A user, account, or role gains end-to-end control over a sensitive process, or the process lacks detective and corrective checks, so abuse or error can proceed without timely challenge.
Impact: Fraud, unauthorized change, undetected error, weaker auditability, and higher residual risk, especially where financial, operational, or privileged actions are involved.
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.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-5 — Separation of Duties | SoD is directly about dividing duties to reduce abuse and error risk. |
| AC-6 — Least Privilege | Internal controls must also limit what each role can do, not only who approves. | |
| AU-6 — Audit Review, Analysis, and Reporting | Broader internal controls rely on monitoring and review beyond SoD. | |
| Recommendation — Apply AC-5 to split sensitive process steps across different roles. Apply AC-6 to restrict each role to the minimum necessary access. Use AU-6 to review logs and investigate suspicious or exceptional activity. | ||
| ISO/IEC 27001:2022 | A.5.3 — Segregation of duties | ISO 27001 explicitly treats SoD as a distinct organisational control. |
| A.5.15 — Access control | Internal controls include access governance beyond duty separation. | |
| Recommendation — Define and enforce duty splits for sensitive tasks. Set access rules that support approvals, reviews, and monitoring. | ||
Practitioner Guidance
What to verify: Check whether the control issue is really about role overlap, missing approvals, weak reconciliation, or absent monitoring. That distinction determines whether the fix is access redesign, process redesign, or both.
Decision rule: If one person or account can initiate and approve the same high-risk action, treat it as an SoD failure first. If the process has separate roles but no reliable review or exception detection, treat it as an internal control weakness more broadly.
Practitioner takeaway: Use SoD to prevent concentrated power, and use internal controls to make the whole process observable, reviewable, and correctable.
Related resources from NHI Mgmt Group
- Why do deficiencies in segregation of duties and IT general controls create material weakness risk?
- Why do Oracle segregation of duties controls create so much review noise?
- Why do segregation of duties controls fail in cloud and SaaS environments?
- Why do segregation of duties controls break down in hybrid and multi-application environments?
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 November 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org