liveBook · Manning

Separation of duties

Separation of duties is a control principle that distributes conflicting responsibilities among multiple people or roles so no individual can complete a sensitive operation alone.

How 4 Manning books explain it

Fundamentals of Cybersecurity

Segregation of duties is an organizational control that divides roles and responsibilities among different people to reduce errors, fraud, and conflicting authority.

How it is used
Reduces fraud, abuse, and error by limiting one person's control over a process within access control.
How deep it goes
Defines the principle and explains a workplace example, policy-based role separation, and static or dynamic enforcement.
Examples
Uses reimbursement approval and processing, plus approval before access to privileged tools, as examples.
What you can do after
Apply the principle by separating conflicting roles in policy or requiring two authorized people to initiate and complete an action.

Read how Fundamentals of Cybersecurity explains separation of duties →

Authorization in Action

Separation of duties is a control principle that assigns a sensitive process to multiple people so that no single person performs all conflicting responsibilities.

How it is used
Structures policy creation, approval, deployment, and review so conflicting responsibilities remain distributed across roles.
How deep it goes
Explains role boundaries and an operational workflow, while stopping short of detailed constraint syntax or runtime enforcement.
Examples
Uses an ACME policy workflow separating authoring, review, approval, coordination, and audit.
What you can do after
Evaluate authorization workflows for conflicting responsibilities and assign independent review, approval, coordination, and audit roles.

Read how Authorization in Action explains separation of duties →

Grokking Web Application Security

The four-eyes principle is a control requiring critical changes or actions to be reviewed by at least two people before implementation.

How it is used
Uses independent approval to catch security lapses before critical changes reach production.
How deep it goes
Explains approval roles, documentation, rejection authority, and code-review enforcement without detailing implementation internals.
Examples
Uses missile-launch key controls, critical-system changes, and GitHub pull requests with required approval and passing tests.
What you can do after
Apply it via GitHub, ticketing workflows, source control, and review policies to prevent unapproved critical changes.

Read how Grokking Web Application Security explains separation of duties →

Kargo in Action

Separation of duties is a control that distributes approval, execution, and review responsibilities among different people or roles.

How it is used
Diagnoses whether the CI/CD promotion gap leaves deployment approvals and responsibilities unclear.
How deep it goes
Tests whether code authors can deploy without independent review, but gives no enforcement procedure.
Examples
Checks whether the same person can write code and deploy it, and whether production matches the validated artifact.
What you can do after
Diagnose whether one person can deploy their own code without independent review or bypass pre-production.

Read how Kargo in Action explains separation of duties →

Also covered in

What to know first

Related concepts

Questions about separation of duties

What is separation of duties?

Separation of duties is a control principle that distributes conflicting responsibilities among multiple people or roles so no individual can complete a sensitive operation alone.

Which Manning books explain separation of duties?

Fundamentals of Cybersecurity, Authorization in Action, Grokking Web Application Security and Kargo in Action.

What should I know before learning separation of duties?

Manning books that teach separation of duties usually introduce authorization, code review, commit and production first.

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

Separation of duties is a control principle that distributes conflicting responsibilities among multiple people or roles so no individual can complete a sensitive operation alone. Dual control is a security principle requiring two or more authorized people or mechanisms to participate in a sensitive action.

What is separation of duties a kind of?

Separation of duties is a kind of change control. Change control is a formal process for documenting, reviewing, approving, and managing changes to systems, requirements, or project scope.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.