Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Separation of Duties?

Separation of duties splits a sensitive process so that no single person can complete it alone, making fraud and unilateral mistakes require collusion rather than opportunity.

Illustration for the cybersecurity term Separation of Duties
Home / Blog / Cybersecurity Terms / What Is Separation of Duties?
17 November 2026

What Is Separation of Duties?

What Is Separation of Duties?

Separation of duties—segregation of duties in accounting language—breaks a sensitive process into steps that different people must perform. One person raises the purchase order, another approves it, a third releases the payment. The point is not distrust of individuals. It is that a process requiring two people to subvert it is dramatically harder to subvert, and that a second pair of eyes catches honest mistakes before they reach production.

The Toxic Combinations

Risk concentrates in specific pairings, often called toxic combinations because each permission is reasonable alone and dangerous together.

CombinationWhat it enables
Create supplier records and approve paymentsInvoices paid to an account the same person set up
Write code and deploy it to production unreviewedA backdoor or an unlogged change reaching live systems
Administer systems and manage their audit logsActivity erased by the person who performed it
Request access and grant itSilent privilege accumulation
Run payroll and amend employee bank detailsSalary diverted to a controlled account
Hold the encryption key and the encrypted backupUnilateral access to, or destruction of, recovery data

The control that matters most for security teams is the third: an administrator who can alter or delete the record of what they did defeats non-repudiation entirely. Forwarding logs to a platform administered by a different team, with append-only retention, is the standard answer.

Enforcing It Technically

Policy statements do not separate anything. The enforcement lives in the systems:

Entitlement analysis then checks the result. Enterprise resource planning suites have had conflict rule sets for decades; cloud and identity platforms are catching up, and the same analysis can be run with a spreadsheet of role assignments if nothing better exists.

What the Standards Require

ISO/IEC 27001:2022 includes segregation of duties as Annex A control 5.3, requiring conflicting duties and areas of responsibility to be separated to reduce the risk of fraud, error, and bypassing of controls. PCI DSS v4.0 requires separation between development, test, and production environments and between the personnel working in them, and restricts who may change audit logs. For financial entities, DORA expects ICT risk management functions to be independent of the functions they oversee. Listed companies with US reporting obligations face segregation-of-duties testing under Sarbanes–Oxley, and UK charities and public bodies meet similar expectations through financial regulations and internal audit.

Small Teams and Compensating Controls

A four-person IT department cannot split every duty, and pretending otherwise produces a policy everybody ignores. The honest approach is to document the conflict as a risk, apply compensating controls, and accept what is left as residual risk with a named owner. Compensating controls that genuinely help include:

Separation of duties sits alongside least privilege and the need-to-know principle as one of the three access controls that limit what a compromised account can achieve. An attacker who phishes one credential inherits that person’s duties—and only those. If you want to know which conflicts currently exist in your estate, our cyber risk analysis services include entitlement review.

FAQ – Frequently Asked Questions

What Is the Difference Between Separation of Duties and Least Privilege?

Least privilege limits how much any single account can do, reducing the damage from one compromised credential. Separation of duties splits a process so that completing it needs more than one person, which protects against deliberate misuse by an authorised insider. They address different threats and are usually implemented together through role design and workflow approvals.

How Do Small Organisations Apply This?

By accepting that full separation is impossible and compensating instead. Document the conflicting duties as a named risk, bring in an independent reviewer from outside the team, alert on self-approval and out-of-hours changes, forward logs somewhere administrators cannot edit them, and enforce leave rotation. Record the residual risk and have a senior owner accept it formally.

Does Separation of Duties Apply to DevOps Teams?

Yes, though it looks different. Rather than separating people from environments, you separate authority: branch protection that blocks self-approval, deployment credentials held by the pipeline rather than individuals, infrastructure changes made only through reviewed code, and production access granted just in time with approval. PCI DSS v4.0 still expects separation between development and production.

Which Standards Require Separation of Duties?

ISO/IEC 27001:2022 lists it as Annex A control 5.3. PCI DSS v4.0 requires separated development, test, and production environments and restricts who can modify audit logs. DORA requires independence for ICT risk functions in financial entities, and Sarbanes–Oxley drives segregation testing for companies with US reporting obligations. Most internal audit frameworks test it as standard.

Related Terms

You May Be Interested In These

What Is Kerberos Authentication?

Cybersecurity Terms

17 November 2026

What Is Kerberos Authentication?

Read More
What Is TACACS+?

Cybersecurity Terms

17 November 2026

What Is TACACS+?

Read More
What Are Salting and Peppering?

Cybersecurity Terms

17 November 2026

What Are Salting and Peppering?

Read More