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

Separation of Privilege

Explore requiring multiple conditions or parties for sensitive operations to prevent single points of failure.

Separation of Privilege

What you'll learn: How requiring multiple independent conditions or parties for critical operations prevents single points of failure and strengthens security.

The Core Idea

Separation of Privilege is a security design principle that requires multiple distinct conditions, credentials, or parties to be satisfied before a sensitive operation can proceed. Rather than trusting a single check or authorization, you split the privilege across multiple independent mechanisms—meaning no single compromise or failure can grant unauthorized access.

Think of a bank vault requiring two different keys held by two different managers—both must be present to open it. Neither manager alone has full privilege; they must cooperate, creating redundancy and reducing the risk of insider threats or single-key theft.

How It Works in Practice

This principle extends beyond dual-person control to include:

  • Multi-factor authentication: Something you know (password) and something you have (token)
  • Dual authorization workflows: Database administrator and security officer must approve schema changes
  • Cryptographic key splitting: Payment authorization requires keys from both finance and compliance systems
  • Code deployment gates: Automated tests and peer review and security scan must all pass

The key is independence—the conditions shouldn't rely on the same underlying mechanism. If both "keys" come from the same compromised authentication server, you haven't truly separated privilege.

Why It Matters

Separation of Privilege directly counters:

  • Single point of compromise: One stolen credential isn't enough
  • Insider threats: No individual has unchecked power
  • Accidental misuse: Multiple checks catch mistakes before damage occurs

This builds on Least Privilege (limiting access) and Complete Mediation (always checking), but adds the critical layer of requiring multiple independent validations.

Key Takeaway: Separation of Privilege mandates that sensitive operations require multiple independent conditions or parties, eliminating single points of failure and creating defense in depth through required cooperation or multi-factor validation.