Home / Glossary / Segregation of duties
Glossary, read 12 Nov 2026
Segregation of duties in a SOC 2 examination, defined with a sourced example
The definition of Segregation of duties
In SOC 2 it shows up in change management, access and finance-adjacent controls. The author of a code change should not be the only approver. The person who grants production access should not be the only person who reviews who has it. The person who runs payments should not reconcile them.
Small teams push back with a fair point: with six engineers, strict separation is awkward. The usual answer is a compensating control, such as a second person approving every merge and an automated alert on direct pushes to the main branch. Document the reasoning in the policy, and let the auditor see it work.
NIST's glossary notes that separation can be static, by defining conflicting roles, or dynamic, by enforcing the check at access time, and gives the two-person rule as a dynamic example. Auditors look for the enforcement mechanism, not the intention, so show the tool setting, not a sentence in the policy.
A sourced example
NIST SP 800-53 AC-5 guidance says separation of duties includes "ensuring that security personnel who administer access control functions do not also administer audit functions." For a startup, that means the engineer who grants production access should not be the sole person reviewing the access logs for misuse. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026.
Related terms
Sources
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
- NIST CSRC glossary, separation of duty, read 12 Nov 2026
Last reviewed 12 Nov 2026.