DOMAIN 7 · Security Operations
Business Continuity: BIA, Recovery Objectives, and Exercises
Connect business impact to RTO, RPO, recovery strategies, and evidence that a recovery plan works.
Start with the business process
Section titled “Start with the business process”Business continuity concerns sustaining important activities during disruption. Information-system contingency and disaster recovery plans support that purpose by restoring required capabilities. A backup is one resource within this design, not a complete continuity plan.
NIST SP 800-34 Rev. 1 places the business impact analysis, or BIA, before selecting recovery strategies. The BIA identifies supported processes, disruption impacts, resource requirements, interdependencies, and recovery priorities.1 For CISSP, the key connection is from business need to technical recovery capability.
Distinguish three time concepts
Section titled “Distinguish three time concepts”| Concept | Meaning for planning | Avoid confusing it with |
|---|---|---|
| Maximum Tolerable Downtime, MTD | How long a mission or business process can be disrupted without significant harm | A target for one server’s restart |
| Recovery Time Objective, RTO | The allowed recovery time for a system resource before unacceptable impact | The acceptable amount of lost data |
| Recovery Point Objective, RPO | The point in time to which data must be recovered after disruption | The time required to restore service |
RTO must support the business’s tolerable disruption, allowing for other necessary recovery and work-resumption activities. RPO informs how much recent data can be absent from the recovered state. Reducing RPO does not automatically reduce RTO.1
Worked example: an ordering service
Section titled “Worked example: an ordering service”Suppose a fictional organization determines that four hours of order-processing disruption would cause significant harm. It chooses a two-hour system RTO to leave time for business validation and resumption, and an RPO allowing no more than fifteen minutes of missing transactions.
A nightly backup cannot, by itself, support that data objective. A frequently updated recovery copy may improve the data position but still require substantial restoration and validation time. The team must also restore dependencies such as identity, network connectivity, encryption keys, and external interfaces. These figures are illustrative business choices, not NIST-mandated values.
Select a recovery strategy
Section titled “Select a recovery strategy”Compare alternate locations, processing capacity, backup arrangements, telecommunications, staffing, and supplier dependencies against the BIA. A ready-to-operate recovery environment generally offers different cost and preparation tradeoffs from an empty facility. Labels such as hot, warm, and cold sites help discussion, but the organization’s actual capacity and activation procedures determine the outcome.1
Examine shared dependencies. Two application instances do not provide meaningful independence if both require the same unavailable identity service or administrative credential. State assumptions explicitly so that recovery plans do not rely on resources the same incident could remove.
Write executable recovery procedures
Section titled “Write executable recovery procedures”NIST organizes contingency-plan execution around activation and notification, recovery, and reconstitution. Plans need roles, contacts, activation criteria, dependencies, restoration steps, validation, and a controlled return to normal operations.1
JIPDEC’s public ISMS guide also places business-continuity plans and procedures among examples of documented operational processes. This connects recovery work with ongoing management and records; it does not establish that one NIST plan satisfies every ISO/JIS requirement.2
Exercise and maintain the plan
Section titled “Exercise and maintain the plan”Tabletop exercises examine decisions and coordination. Technical tests can demonstrate whether restoration works under selected conditions. Measure elapsed recovery time, the recovered data point, integrity checks, missing dependencies, and the ability of business users to resume work. Update the plan after system changes and lessons from exercises.1
A successful backup job is not evidence of successful recovery. Restore a suitable copy, confirm it is usable, and record what the test actually covered. An exercise that excludes supplier unavailability cannot establish that the plan handles that scenario.
Common misunderstandings
Section titled “Common misunderstandings”- “RTO and RPO are interchangeable.” One addresses recovery time; the other addresses recovered data position.
- “High availability eliminates disaster recovery.” Redundant components can still share causes of failure.
- “The written plan proves readiness.” Exercises reveal whether people, dependencies, and procedures work together.
Connect this topic
Section titled “Connect this topic”Incident response coordinates containment with restoration. Control assessment explains how to evaluate the evidence produced by recovery exercises.
References
Section titled “References”Footnotes
Section titled “Footnotes”-
NIST, SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems, updated November 2010; sections 2–4, especially the BIA, recovery strategies, exercises, and plan phases. ↩ ↩2 ↩3 ↩4 ↩5
-
JIPDEC, ISMS User’s Guide: JIS Q 27001:2023 / ISO/IEC 27001:2022, March 2025; chapter 8 and Figure 8-1, examples of documented operational processes. Public explanatory guidance. ↩
Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.
Editorial policy & attribution