Course contentsShow
← Security
Lesson 2664 of 3,05250. Secure Architecture and DesignFree lesson

Separation of Duties

Divide critical operations among multiple parties to prevent fraud and errors through checks and balances.

Separation of Duties

What you'll learn: How dividing critical operations among multiple parties prevents fraud, errors, and insider threats through mandatory checks and balances.

The Core Idea

Separation of Duties (SoD) is an architectural control that requires two or more people to complete a critical task. No single individual can execute a sensitive operation from start to finish. This prevents abuse of power, reduces errors through peer review, and creates accountability trails.

Think of it like launching nuclear missiles: two keys must turn simultaneously, held by different officers. One person alone cannot initiate launch, even with full access credentials.

How It Works in Practice

SoD splits responsibilities across roles:

  • Financial systems: One person requests a payment, another approves it, a third processes it
  • Code deployment: Developer writes code, peer reviews it, operations team deploys (with automated checks)
  • Access management: One admin creates accounts, another assigns privileges
  • Backup restoration: One person initiates restore, another verifies integrity before applying

This differs from Principle of Least Privilege (granting minimal necessary access) by focusing on workflow distribution rather than permission minimization. SoD enforces that even privileged users cannot act alone.

Detection and Enforcement

Modern systems enforce SoD through:

  • Role-Based Access Control (RBAC): Mutually exclusive roles prevent one user from holding conflicting permissions
  • Workflow engines: Multi-step approvals with different authenticators
  • Audit logs: Tracking who performed each step reveals collusion attempts
  • Automated conflict detection: Flagging when a single user tries to execute multiple phases

Why It Matters

SoD creates detection opportunities. While collusion between multiple parties is still possible, it's significantly harder to orchestrate and leaves more evidence than single-actor fraud.

Key Takeaway: Separation of Duties architecturally prevents any single person from compromising critical operations by requiring collaborative execution and creating natural checkpoints for review and accountability.