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

Redundant Controls and Failure Tolerance

Designing overlapping security controls so compromise of one layer doesn't compromise the entire system.

Redundant Controls and Failure Tolerance

What You'll Learn

You'll learn how to design overlapping security controls so that the failure or compromise of one layer doesn't collapse your entire defense strategy.

The Core Concept

Redundant controls mean implementing multiple, independent security measures that protect the same asset or boundary. Think of it like a bank vault: if someone bypasses the door lock, they still face motion sensors, cameras, time-delayed safes, and security guards. No single point of failure can grant complete access.

In security architecture, failure tolerance means designing systems where:

  • Multiple controls protect critical assets (redundancy)
  • Controls use different mechanisms (diversity)
  • Compromise of one control doesn't reveal how to bypass others (independence)

Why Redundancy Matters

Defense-in-depth provides layers, but redundant controls provide backup within layers. For example:

  • Authentication: Require both password AND hardware token (not just one strong method)
  • Network filtering: Deploy firewall rules AND host-based firewalls (not just perimeter protection)
  • Data protection: Implement both encryption at rest AND strict access controls (not just encryption alone)

If an attacker finds a firewall misconfiguration, host-based controls still block them. If they steal an encrypted database backup, they still can't decrypt it without keys stored elsewhere.

Designing for Failure

Assume every control will eventually fail—through misconfiguration, zero-day exploits, insider threats, or simple human error. Your architecture should answer: "What happens when this specific control fails?" If the answer is "complete compromise," you need redundancy.

Effective redundant controls are:

  • Independent: Different technologies, vendors, or mechanisms
  • Overlapping: Cover the same threat scenarios
  • Monitored: Alert when one control fails so you can respond before others fail too

Key Takeaway:
Design security architectures where no single control failure leads to system compromise—build redundant, independent controls that create multiple barriers attackers must overcome, ensuring failure tolerance at every critical layer.