Study guide

8.5 Disaster Recovery, Backup, Availability, and Resilience

CISSP Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CISSP Orientation, CAT, and Official Source Control

1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview

2 Chapter 2: Security and Risk Management

2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab

3 Chapter 3: Asset Security and Data Lifecycle

3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab

4 Chapter 4: Security Architecture, Engineering, and Cryptography

4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab

5 Chapter 5: Communication, Network Security, and Zero Trust

5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab

6 Chapter 6: Identity and Access Management

6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab

7 Chapter 7: Security Assessment, Testing, and Audit Strategy

7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab

8 Chapter 8: Security Operations, Incident Response, and Resilience

8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab

9 Chapter 9: Software Development Security and DevSecOps

9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab

10 Chapter 10: Integrated CISSP Governance Scenario Labs

10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation

11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy

11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review

8.5 Disaster Recovery, Backup, Availability, and Resilience

Key Takeaways Explain This Topic AI

Disaster recovery restores technology services, while business continuity keeps critical business processes operating.

Recovery objectives should be based on business impact analysis, not technology preference.

Backups are useful only when they are protected, restorable, tested, and aligned to RTO and RPO.

Resilience combines redundancy, diversity, monitoring, exercises, supplier planning, and executive decision authority.

Last updated: May 2026

Recovery as a Business Decision

Disaster recovery and resilience are not only data center topics. They address the ability of the organization to continue critical processes during disruption and restore services to acceptable levels. Disruptions may include ransomware, cloud outages, network failures, power loss, fire, flood, supplier failure, regional disaster, human error, pandemic conditions, or destructive insider activity. The CISSP view starts with business impact, then selects technical and operational controls that match that impact.

Business continuity focuses on sustaining critical business processes. Disaster recovery focuses on restoring technology services that support those processes. The two must be connected. A trading platform, hospital scheduling system, payroll process, call center, and manufacturing control system may all need different recovery priorities. The recovery plan should not simply restore the easiest systems first. It should restore what the business needs first.

A business impact analysis identifies critical processes, dependencies, maximum tolerable downtime, financial impact, legal impact, safety impact, customer impact, and resource requirements. It supports recovery time objective and recovery point objective decisions. RTO is the target time to restore a service. RPO is the acceptable amount of data loss measured in time. These objectives should be approved by business owners because they drive cost and architecture.

Backups are a major recovery control, but backup existence is not backup readiness. Backups must be complete, protected from alteration, retained long enough, encrypted where appropriate, isolated from compromised administrators, and tested through restoration. Ransomware has made immutable or offline backup copies especially important for critical data. A backup that can be deleted by the same compromised account as production data may not provide resilience.

  • Concept Practical question Example decision
  • BIA What business process fails and how badly? Customer payments cannot stop more than four hours
  • RTO How quickly must service return? Restore order entry within two hours
  • RPO How much data loss is acceptable? Lose no more than fifteen minutes of transactions
  • MTD What is the outer limit before severe harm? Manual process can sustain one business day
  • DR test Can the plan work under real constraints? Restore from isolated backup in a timed exercise

Availability architecture includes redundancy, clustering, load balancing, failover, replication, alternate sites, diverse network paths, alternate power, spare hardware, and cloud region design. Higher availability usually costs more and may add complexity. Active-active systems reduce downtime but require careful data consistency and monitoring. Cold sites cost less but take longer to activate. Warm sites sit between cost and speed. The right answer depends on business impact and risk appetite.

Resilience also includes people and suppliers. A recovery plan may fail if only one administrator knows the procedure, if vendor contacts are outdated, if emergency procurement is blocked, if remote access depends on the failed identity system, or if fuel contracts do not cover a regional emergency. Plans should identify alternates for key roles, cross-train staff, document runbooks, and validate supplier commitments.

Testing is where plans become credible. Tabletop exercises test decision-making and coordination. Walkthroughs verify procedures and roles. Technical restore tests validate backup integrity. Parallel tests run recovery systems without stopping production. Full interruption tests provide strong evidence but carry risk and need executive approval. Test scope should grow as maturity improves. Findings should be tracked like other risk remediation work.

Backup and Recovery Control Checklist

Classify systems by business process, data sensitivity, RTO, RPO, and dependency chain.

Protect backup administration with separate credentials, MFA, logging, and least privilege.

Maintain immutable, offline, or otherwise isolated copies for critical data and configurations.

Test restoration of files, databases, identity services, cloud resources, and full applications.

Document manual workarounds for critical processes when technology is unavailable.

Review recovery plans after major system changes, supplier changes, exercises, and incidents.

Recovery sequencing matters. Identity, network, DNS, security tools, key management, and administrative access may need restoration before business applications can return. A plan that restores applications before authentication or network segmentation may not work. Dependency mapping helps define the order. It also helps leaders understand why a lower-profile platform may be a prerequisite for a high-profile service.

Crisis communication is part of resilience. Employees need instructions for alternate work locations, manual procedures, and safe communication channels. Customers may need service status. Regulators or contractual partners may require notice depending on impact. Executives need options such as degrade service, switch provider, invoke manual processing, or suspend a function. Communication templates should be prepared, but facts must be updated before use.

Resilience is not the same as perfection. Some downtime or data loss may be accepted for low-impact systems because the cost of near-zero outage is unjustified. For safety, regulated, revenue-critical, or mission-critical services, higher investment is appropriate. A CISSP should connect the cost of controls to the business impact they reduce, then verify that the chosen objectives are realistic through exercises and evidence.

The strongest recovery programs are boring in a useful way. They know their critical services, protect their backups, practice the uncomfortable steps, and correct gaps before a disaster. When a disruption occurs, the organization does not need heroic improvisation. It uses rehearsed authority, tested data, known dependencies, and risk-based priorities.