Requirement
Conflicting duties and conflicting areas of responsibility shall be segregated.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
segregation of dutiesseparation of dutiesconflicting dutiesfour eyestwo-person
Supporting terms — specificity signals
maker checkerdual approvalcompensating controlmatrix
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| NIST CSF 2.0 | PR.AA-05 | Access permissions follow least privilege and separation of duties | access-control segregation |
| GDPR | Art.29 | Processing under the authority of the controller | access-control |
| CCPA/CPRA | 1798.100(e) & 1798.150 | Reasonable security procedures | access-control |
| SOC 2 | CC6.2 | Registration and authorisation of new users | access-control |
| PCI DSS 4.0.1 | 1.3 | Restrict network access to and from the cardholder data environment | segregation |
| PCI DSS 4.0.1 | 6.5 | Change management and separation of environments | segregation |
| PCI DSS 4.0.1 | 7.2 | Access granted by least privilege and reviewed every six months | access-control |
| PCI DSS 4.0.1 | 8.2 | Unique IDs and user account lifecycle | access-control |