Separation of duties requires independent review when the person who wrote code could otherwise deploy it. Check whether production approvals are attributable, whether production runs the artifact validated in pre-production, and whether a deployment could bypass pre-production. section 1.1.1
Separation of duties
Separation of duties is a control that distributes approval, execution, and review responsibilities among different people or roles.
How Kargo in Action covers it
- 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.
- How it connects
- Links separation of duties to CI/CD, pre-production validation, production deployment, and artifact lineage.
Also explained in
-
Fundamentals of CybersecuritySegregation of duties is an organizational control that divides roles and responsibilities among different people to reduce errors, fraud, and conflicting authority.
-
Authorization in ActionSeparation of duties is a control principle that assigns a sensitive process to multiple people so that no single person performs all conflicting responsibilities.
-
Grokking Web Application SecurityThe four-eyes principle is a control requiring critical changes or actions to be reviewed by at least two people before implementation.
Compare how 4 books explain separation of duties →
Related concepts
- branch protectionimplemented by · Branch protection is a repository policy that restricts changes or operations on a branch unless specified conditions, such as checks or approvals, are met.
- dual controlcontrasts with · Dual control is a security principle requiring two or more authorized people or mechanisms to participate in a sensitive action.
- pull requestuses · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
- administrative controlkind of · An administrative control is an organizational safeguard comprising policies, procedures, training, or oversight that governs security-related behavior and activities.
- code reviewuses · Code review is the systematic examination of source code or proposed changes to assess correctness, quality, risks, or conformance to requirements or standards.
This explainer was generated by Manning's knowledge graph from the text of Kargo in Action. The section links point to the parts of the book it draws on.



