Business Continuity & Disaster Recovery
CISSP CISSP · Security Operations
Continuity is a business discipline
Business continuity planning (BCP) and disaster recovery planning (DRP) answer a simple question: when something goes badly wrong, how does the organisation keep operating — and how does it get back to normal? Domain 1 covered the requirements side (the business impact analysis, RTO, RPO, MTD); Domain 7 covers the planning and recovery side. The exam's framing is that continuity is a business responsibility, not an IT project: the business decides what must keep running and how fast it must recover, and IT builds the recovery capability to match. A disaster recovery plan that restores the wrong systems first, or that recovers IT perfectly while the business cannot operate, is a failed plan.
BCP versus DRP
The two plans are related but distinct. The Business Continuity Plan (BCP) is the organisation-wide plan for keeping critical business functions operating during and after a disruption — it covers people, processes, facilities, suppliers and communications, not just technology. The Disaster Recovery Plan (DRP) is the technology-focused subset: how IT systems, data and infrastructure are recovered. The BCP answers "how does the business keep serving customers?"; the DRP answers "how do we get the servers and data back?" The exam tests the scope difference: a plan that covers alternate office space, manual workarounds and supplier communication is a BCP; a plan that covers server restoration and data recovery is a DRP. Both plans need an owner, a maintenance schedule, and regular testing — a plan that has never been tested is a document, not a capability.
Recovery strategies and alternate sites
Recovery sites are classified by how ready they are, and the exam tests the trade-off between cost and recovery speed. A hot site is fully equipped, with hardware, software and current data, ready to take over within hours or minutes — the fastest recovery and the most expensive. A warm site has hardware and connectivity but no current data; data must be restored from backups, so recovery takes longer (typically a day or more) but costs less. A cold site is essentially an empty facility with power, cooling and network — hardware and data must be brought in, so recovery takes days to weeks, but the cost is lowest. Mobile sites are transportable units (trailers with equipment) that can be delivered to a location. Reciprocal agreements — two organisations agreeing to host each other's recovery — are the cheapest option but the least reliable, since both organisations may be affected by the same regional disaster and neither has spare capacity guaranteed. The exam's key insight: the site type must match the RTO. A four-hour RTO cannot be met by a cold site, and a hot site is wasted money for a function with a two-week RTO.
| Site type | Readiness | Typical recovery time | Relative cost |
|---|---|---|---|
| Hot site | Fully equipped with current data | Minutes to hours | Highest |
| Warm site | Hardware ready; data must be restored | Hours to a day | Medium |
| Cold site | Empty facility with power and cooling | Days to weeks | Lowest |
| Mobile site | Transportable unit delivered on demand | Days | Medium |
| Reciprocal agreement | Partner's facility, if available | Unpredictable | Lowest (but unreliable) |
Backup strategies
Backups are the foundation of data recovery, and the exam tests the backup types and their trade-offs. A full backup copies all selected data; it is the slowest to perform and the largest to store, but the fastest to restore from (a single backup set). An incremental backup copies only data that has changed since the last backup of any type; it is fast and small, but restoration requires the last full backup plus every incremental since — the slowest restore. A differential backup copies all data changed since the last full backup; it grows over time but restoration needs only the full backup plus the latest differential — a middle ground. The 3-2-1 rule is the standard for backup resilience: three copies of the data, on two different media types, with one copy offsite. The exam also covers backup verification (a backup that has never been test-restored is not a backup — it is a hope), backup encryption (backups contain the same sensitive data as production and must be protected equally), and retention (how long backups are kept, driven by the RPO and by legal requirements). Modern approaches include continuous data protection (CDP) and replication (synchronous replication writes to both primary and secondary simultaneously, giving near-zero RPO but requiring low-latency links; asynchronous replication has a small lag but works over longer distances).
Plan development and the BCP process
Developing a continuity plan follows a sequence the exam tests: first, obtain senior management support (without it, the plan has no funding and no authority); second, conduct the business impact analysis to identify critical functions and their recovery requirements; third, develop recovery strategies matched to those requirements; fourth, write the plan — with clear roles (who declares a disaster? who authorises the recovery site? who communicates with staff, customers and regulators?), contact lists, recovery procedures, and manual workarounds; fifth, test the plan; and sixth, maintain the plan through regular review and updates when the business, the technology or the threats change. The exam's most common BCP trap is starting with technology: the correct first step is always management support and the BIA, not buying a hot site or a backup product.
Testing the plan
Plans must be tested, and the exam distinguishes the test types by increasing realism and cost. A checklist review (or desk check) simply verifies the plan document is complete and current. A structured walkthrough has the team talk through the plan step by step. A tabletop exercise presents a scenario and has participants discuss their responses (see the incident response guide). A simulation (or functional exercise) actually performs parts of the recovery, such as failing over a system to the recovery site. A full interruption test (or full-scale exercise) shuts down production and runs the business from the recovery site — the most realistic test and the riskiest, since a failure during the test becomes a real outage. The exam's point: testing should progress from the least disruptive to the most realistic, and every test should produce findings that improve the plan. An untested plan is the most common continuity failure.
Personnel and crisis management
Continuity plans often fail on the human side. The exam covers crisis management — the leadership function during a disruption, typically run by a crisis management team that makes strategic decisions (declaring a disaster, authorising expenditure, communicating externally) while the recovery teams handle the technical work. Emergency response is the immediate priority: life safety comes before everything else, including data and systems. Communication plans must cover internal staff (where to go, what to do), customers (what is affected, when service will return), suppliers, regulators, and the media — with pre-drafted templates and a single spokesperson. Succession planning ensures that if key individuals are unavailable, their deputies can act. And employee safety and support — accounting for all staff, providing assistance — is a responsibility the exam treats as non-negotiable. A plan that recovers the servers but loses track of the people has failed.
Exam mindset for continuity
Continuity questions reward following the process in order: management support, BIA, strategy, plan, test, maintain. Match the recovery strategy to the RTO and RPO — an expensive hot site for a non-critical function is as wrong as a cold site for a four-hour RTO. And remember that testing is not optional: the correct answer to a question about an untested plan is almost always "test it".
Exam traps to watch for
- Starting with technology instead of management support and the BIA — the business requirements come first, always.
- Matching the wrong site to the RTO: a cold site cannot meet a four-hour RTO; a hot site is wasted on a two-week RTO.
- Confusing incremental and differential backups: incremental backs up changes since the last backup of any type; differential backs up changes since the last full backup.
- Treating an untested backup or plan as reliable — a backup never test-restored and a plan never exercised are assumptions, not capabilities.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.An organisation is developing its first business continuity plan. What should be the FIRST step?
Explanation: Without senior management support, the continuity program has no funding, no authority and no mandate — every subsequent step depends on it. Purchasing a hot site before the BIA is premature: the organisation does not yet know which functions need fast recovery. A full interruption test requires a plan to test. Writing DR procedures before the BIA means writing procedures for requirements that have not been defined.
Exam objective: CISSP Domain 7: Understand business continuity planning (program development)
Q2.A trading system has an RTO of 2 hours and an RPO of 15 minutes. Which recovery strategy BEST meets these requirements?
Explanation: A 2-hour RTO and 15-minute RPO demand near-immediate failover and near-continuous data protection — only a hot site with synchronous replication or CDP can deliver that. A cold site takes days to bring up. A warm site with nightly backups would lose up to 24 hours of data (far beyond the 15-minute RPO) and take hours to restore. A reciprocal agreement offers no guaranteed capacity or timeline.
Exam objective: CISSP Domain 7: Understand business continuity planning (recovery strategies)
Q3.A backup strategy performs a full backup on Sunday and incremental backups Monday through Saturday. The system fails on Saturday afternoon. How many backup sets are needed to restore the system to its Friday state?
Explanation: Incremental backups contain only the changes since the last backup of any type, so restoring to Friday requires the Sunday full backup plus every incremental from Monday through Friday — six sets in total. The Friday incremental alone contains only Friday's changes. Seven sets would include Saturday's incremental, which does not exist yet (the failure happened Saturday afternoon, and the question asks for the Friday state).
Exam objective: CISSP Domain 7: Understand business continuity planning (backup strategies)
Q4.A company’s disaster recovery plan has been written but never tested. The CISO wants to validate the plan with minimal risk to production operations. What is the BEST first test?
Explanation: A tabletop exercise is the right first test for an untested plan: it validates roles, decision-making and procedures in a discussion format with no risk to production, and it will reveal gaps before any live testing. A full interruption test is the most realistic but also the riskiest — it should come only after less disruptive tests have validated the plan. A live failover simulation is a later step. An untested plan is not validated by who wrote it.
Exam objective: CISSP Domain 7: Understand business continuity planning (plan testing)
Q5.During a fire in the office building, the disaster recovery team begins executing the recovery plan. What is the FIRST priority?
Explanation: Life safety is always the first priority in any emergency — people before property, data or systems. Saving backup tapes, notifying customers and activating the recovery site are all important, but they come after confirming that everyone is safe and accounted for. This principle holds across every domain of the CISSP.
Exam objective: CISSP Domain 7: Understand business continuity planning (emergency response)
Q6.An organisation follows the 3-2-1 backup rule. Which configuration satisfies it?
Explanation: The 3-2-1 rule is: three copies of the data, on two different media types (so a single media failure or vulnerability does not destroy all copies), with one copy offsite (so a site disaster does not destroy all copies). Three copies on the same server share a single point of failure. Two copies on one medium fails both the count and the media diversity. Three cloud providers are a single media type, so this fails the 'two different media types' leg of the rule.
Exam objective: CISSP Domain 7: Understand business continuity planning (backup strategies)
Q7.A company’s BCP covers alternate office space, manual workarounds for critical processes, supplier communication, and staff welfare. Its DRP covers server restoration and data recovery. A new manager asks why both plans exist. What is the BEST explanation?
Explanation: BCP and DRP have different scopes: the BCP covers the whole business (people, processes, facilities, suppliers), while the DRP is the IT-focused subset covering systems and data recovery. They are complementary, not duplicates. The distinction is scope, not disaster type — both plans apply to any disruption. Authorship is not the distinguishing factor.
Exam objective: CISSP Domain 7: Understand business continuity planning (BCP vs DRP)
Q8.A business impact analysis identifies that the payroll system depends on the HR database, which depends on the identity management system. The recovery plan restores the payroll system first. What is wrong with this plan?
Explanation: Recovery must follow the dependency chain: payroll cannot operate until the HR database is available, and the HR database cannot operate until identity management is available. Restoring payroll first wastes time on a system that cannot function yet. Simultaneous restoration is not always possible (resources are limited, and some systems genuinely depend on others being up first). Outsourcing payroll does not solve the dependency problem.
Exam objective: CISSP Domain 7: Understand business continuity planning (dependencies, recovery sequencing)