Skip to content

Separation of Duties

Separation of Duties (SoD) is a control that splits a sensitive process across two or more people so no single person can complete it alone. The employee who requests a payment does not approve it. The developer who writes code does not push it to production unreviewed. Breaking the steps apart removes the one spot where a lone insider could act unchecked.

NIST SP 800-192 puts it plainly: no user should be given enough privileges to misuse the system on their own, and its example is that the person authorizing a paycheck should not also be the one who can prepare it. The payoff is fraud prevention and error catching, since a second set of hands has to sign off before anything becomes final. The tradeoff is friction and headcount, so most teams reserve strict SoD for high-risk workflows like financial approvals, privileged account changes, and production deployments.

How does separation of duties work?

It starts on paper. Control AC-5 in NIST SP 800-53 Rev. 5 has two parts: identify and document the duties that need separating, then define system access authorizations that enforce the split. Its discussion adds a pairing many organizations miss, which is that the people who administer access control shouldn’t also administer the audit logs. Otherwise an administrator could grant themselves access and erase the evidence.

Enforcement usually rides on Role-Based Access Control. Static SoD blocks one person from ever holding two conflicting roles, such as “create vendor” and “approve vendor payment.” Dynamic SoD lets someone hold both roles but stops them from using both on the same transaction. Static is simpler to audit. Dynamic suits small teams where people legitimately wear several hats.

A common mistake is writing SoD into policy while quietly granting one administrator every role in practice, which collapses the control without anyone noticing. Periodic access reviews under objective 5.5 are how you catch that drift.

What is the difference between separation of duties and dual control?

These four controls get mixed up constantly on practice exams:

Control What it does Example
Separation of duties Different people handle different steps One clerk enters an invoice, a manager approves it
Dual control Two people act together on the same step Two keys turned to open a vault
Split knowledge No one person knows the whole secret Two custodians each hold half of a master key
Job rotation Moves people through roles over time A new analyst takes over reconciliations and spots irregularities

SoD stops a lone actor, but two people who collude can still beat it. That’s why job rotation and mandatory vacations sit beside it as detective controls, since a fraud that needs daily hands-on concealment tends to surface when someone else covers the desk.

What happens when separation of duties fails?

The textbook case is Barings Bank. The Bank of England’s Board of Banking Supervision found a lack of separation between the front and back offices at Barings Futures Singapore, where Nick Leeson, as general manager, effectively controlled both trading and settlement. That let him hide unauthorized trades. According to the Reserve Bank of Australia’s November 1995 summary of the report, losses reached £927 million including close-out costs, and administrators took over the parent company on 26 February 1995.

How is separation of duties tested on the CISSP?

Expect scenario questions mainly in Domain 7: Security Operations (7.4) and in Domain 3’s secure design principles (3.1), with ties to Domain 1: Security and Risk Management, where SoD lives inside governance and preventive administrative controls. Know how it differs from dual control, in which two people must act together at the same moment, and be ready to spot which duties should never rest with a single role.

Watch for the small-company scenario. When a five-person IT shop can’t staff full separation, the exam rarely wants you to hire more people. It wants a compensating control, such as independent review of logs by someone outside IT or management sign-off on privileged changes. The NIST wording sits in the CSRC glossary, and the Barings findings are summarized by the Reserve Bank of Australia.

Related terms: Governance, Insider Threat