CISSP Domain 7: Disaster Recovery & Business Continuity (DR/BCP) — Mindmap Review Study Guide
═══════════════════════════════════
PART 1: MERMAID MINDMAP
═══════════════════════════════════
mindmap
root((Recovery Strategies))
Overview
Cost vs Downtime Tradeoff
Business Decision Driver
Failure Modes
Fail-Soft or Fail-Open
Fail-Secure or Fail-Closed
Fail-Safe
Backup Storage Strategies
Archive Bit
Mirror and Stream Backups
Full Backups
Incremental Backups
Differential Backups
Backup Validation Methods
Offsite Storage
Tape Rotation Schemes
Recovery Point Objective RPO
Spare Parts
Cold Spare
Warm Spare
Hot Spare
RAID Configurations
RAID 0 Striping
RAID 1 Mirroring
RAID 10
RAID 5 Parity
RAID 6 Double Parity
High Availability Systems
Clustering
Redundancy
Recovery Sites
Cold Site
Warm Site
Hot Site
Mobile Site
Mirror Redundant Site
Recovery Time Objective RTO
Geographically Remote Location
═══════════════════════════════════
PART 2: TECHNICAL DEFINITIONS & CONCEPTS
═══════════════════════════════════
Overview
Cost vs Downtime Tradeoff — The inverse relationship between system redundancy and cost; minimizing downtime through full redundancy is highly expensive, whereas saving costs typically results in longer downtimes during a failure. Business Decision Driver — The ultimate determinant for how quickly a system must be recovered or the amount of redundancy required; the system owner must decide what is cost-justified based on specific business needs.
Failure Modes
Failure Modes — Three different ways systems can be designed to fail, prioritizing either security, openness, or human safety.
| Term | Definition | Key Distinction / Example |
|---|---|---|
| Fail-Soft (Fail-Open) | System designed to fail to a LESS secure state. | Example: Firewall lets ALL traffic through. |
| Fail-Secure (Fail-Closed) | System designed to fail to a MORE secure state. | Example: Firewall blocks ALL traffic. |
| Fail-Safe | Physical security mechanisms prioritizing human safety above all else. | Example: Doors unlock when fire alarm goes off. |
Backup Storage Strategies
Metadata — Data about data. Archive Bit — A piece of metadata associated with every file that indicates if a backup is required; the OS automatically flips this bit to 1 when a file is created or modified, and it is reset to 0 after certain backups. Backup Types — Different strategies for backing up data, varying by what is captured, archive bit handling, storage space, and recovery time.
| Term | Data Captured | Archive Bit Action | Storage Space | Recovery Time |
|---|---|---|---|---|
| Mirror (Stream) | Exact copy of all data, no compression. | Not specified. | Very high (large space). | Very fast. |
| Full | Every file regardless of archive bit. | Not specified. | High (uses compression). | Slower than mirror. |
| Incremental | Changes since the last incremental backup. | Reset to 0 for backed-up files. | Minimal. | Lengthy (sequential tapes). |
| Differential | Changes since the last full backup. | Left set to 1 for backed-up files. | Moderate/High. | Fast (max 2 tapes: full + differential). |
Backup Validation Methods — Techniques to ensure backups occur correctly, which can be done during the backup or periodically on shelved tapes.
Cyclical Redundancy Checks (CRC) — A specific validation check used to verify backup integrity.
Checksums — Another validation method used alongside CRC and bit-for-bit comparisons to ensure backup integrity. Bit-for-bit Comparisons — A validation method comparing the backup to the original data exactly.
Spot Checking — A validation method involving checking select files rather than the entire backup.
Offsite Storage — Storing backups in a geographically remote location away from the primary system to prevent loss from localized disasters like fire or flood.
Tape Rotation Schemes — Methods for keeping backup tapes for a specific retention period before overwriting old data; driven by retention policies based on regulatory/contractual requirements, restoration needs, and costs.
Recovery Point Objective (RPO) — The maximum tolerable data loss an organization is willing to accept, measured in time (e.g., seconds, days).
⚠️ EXAM TIP: RPO is a major driver of backup solution costs; a shorter RPO means less tolerable data loss and a more expensive solution. To reduce costs, an owner may need to accept a longer RPO.
Spare Parts
Spare Parts — Replacement components (power supplies, RAM, hard drives) categorized by their readiness state and impact on downtime.
| Term | Definition | Recovery Mechanism & Downtime |
|---|---|---|
| Cold Spare | A spare part kept on a shelf. | System down for minutes/hours while retrieved and installed. |
| Warm Spare | Installed in the system but not powered on. | System goes down; requires manually flipping a switch to activate. |
| Hot Spare | Installed AND powered on, ready to go. | Automatic switchover; system remains up and running with zero downtime. |
RAID Configurations
RAID (Redundant Array of Independent Disks) — Using multiple hard drives simultaneously to achieve greater speed, greater redundancy, or both.
| Term | Method | Minimum Drives | Primary Benefit | Redundancy / Fault Tolerance |
|---|---|---|---|---|
| RAID 0 | Striping (Split into pieces) | 2 | Speed (doubled read/write). | None (doubles chance of data loss; 1 drive failure = total loss). |
| RAID 1 | Mirroring (Exact copies) | 2 | Redundancy. | Survives 1 drive failure. |
| RAID 10 | RAID 1 + RAID 0 (Mirrored then stripped) | 4 | Combines mirroring and striping (4 fragments). | Inherits from RAID 1 and 0. |
| RAID 5 | Parity (Exclusive OR math) | 3 | Speed + Redundancy (Happy medium). | Reconstructs data if 1 drive fails (uses remaining piece + parity). |
| RAID 6 | Double Parity | Not specified | Speed + Double Redundancy. | Survives 2 drive failures. |
⚠️ EXAM TIP: Memorize the minimum number of hard drives required for each RAID level (RAID 0: 2, RAID 1: 2, RAID 5: 3, RAID 10: 4).
High Availability Systems
High Availability Systems — Systems designed not to go down in the event of a failure by achieving system-level redundancy through clustering and redundancy.
Clustering — Multiple systems working together simultaneously to support a workload; if one member fails, the cluster continues running at reduced capacity.
Load Balancer — A mechanism used in clustering (e.g., for web servers) to distribute the workload across the cluster members.
Redundancy — Multiple systems (a primary and one or more secondary) where the primary does all the work; if it fails, the secondary takes over to fully support the workload.
Recovery Sites
Recovery Sites — Strategies for recovering whole data centers, ranging from cheapest/most time to most expensive/least time.
| Term | Equipment / Setup | Missing Elements | Recovery Time | Cost |
|---|---|---|---|---|
| Cold Site | Building shell only. | Cabling, racks, servers, data, people. | Weeks. | Cheapest. |
| Warm Site | Building shell + cheap equipment (cabling, racks). | Servers, data, people. | Days. | Moderate. |
| Hot Site | Building + cheap + expensive equipment setup. | Data, people. | Hours / Seconds. | High. |
| Mobile Site | Hot site on wheels (shipping container). | Data, people. | Hours / Days (transport dependent). | High. |
| Mirror / Redundant | Fully operational, staffed, running 24/7 in parallel. | None (fully operational). | Seconds / Instantaneous. | Huge. |
Recovery Time Objective (RTO) — The metric that drives an owner’s selection between different recovery site solutions based on acceptable downtime.
⚠️ EXAM TIP: RTO drives the selection of recovery site solutions, while RPO drives the cost and selection of backup solutions.
Geographically Remote Location — A location far enough away from the primary site that a regional disaster (earthquake, hurricane, flood, wildfire, massive power outage) will not affect both sites; does not imply an exact distance.