Study guide

4.2 Business Continuity, Disaster Recovery, and Resilience

CIA Part 2 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CIA Part 2 Exam Orientation

1.1 Current CIA Part 2 Exam Facts 1.2 Eligibility, Fees, and Pearson VUE Scheduling 1.3 Scoring, Results Timing, and the 2025 Syllabus Map

2 Chapter 2: Engagement Objectives and Scope

2.1 Topical Requirements in Objectives and Scope 2.2 Elements Used to Build Engagement Objectives 2.3 Scope Limitations, Stakeholder Requests, and Scope Changes

3 Chapter 3: Evaluation Criteria and Planning Context

3.1 Selecting and Testing Evaluation Criteria 3.2 Applying Topical Requirements When Planning 3.3 Strategy, Risk Management, and Performance of the Activity Under Review

4 Chapter 4: Technology, Continuity, and Finance in Planning

4.1 Cybersecurity, IT General Controls, Privacy, and Data Security 4.2 Business Continuity, Disaster Recovery, and Resilience 4.3 Finance and Accounting Concepts for the Activity Under Review

5 Chapter 5: Business Process and System Risks in Planning

5.1 Asset, Supply Chain, Inventory, Payables, Procurement, and Compliance Processes 5.2 Third-Party Process Risks 5.3 CRM, ERP, and GRC System Risks

6 Chapter 6: Engagement Approach and Project Management

6.1 Agile, Traditional, Integrated, and Remote Approaches 6.2 Project Management While Planning and Conducting Engagements

7 Chapter 7: Engagement Risk Assessment

7.1 Topical Requirements and Pervasive Financial, Operational, IT, Cyber, and Regulatory Risks 7.2 Emerging Risks and the Impact of Change 7.3 Methods to Evaluate and Prioritize Risks and Controls

8 Chapter 8: Structure, Environment, and Culture

8.1 Centralized vs Decentralized, Flat vs Traditional, In-Person vs Remote 8.2 Culture, Group Behavior, and Tone at the Top

9 Chapter 9: Control Design, Effectiveness, and Efficiency Procedures

9.1 Procedures to Evaluate Control Design 9.2 Procedures to Test Operating Effectiveness 9.3 Procedures to Test Control Efficiency

10 Chapter 10: Work Programs, Testing Methodologies, and Resources

10.1 Evaluating Adequacy of the Engagement Work Program 10.2 Testing Methodologies for Accounting, Finance, IT, Operations, and Cybersecurity 10.3 Financial, Human, and Technological Resources and Limitation Implications

11 Chapter 11: Information Sources and Preliminary Survey

11.1 Interviews, Observations, and Walk-Throughs 11.2 Data Analysis as an Information Source 11.3 Policies, Checklists, Risk-and-Control Questionnaires, and Self-Assessments

12 Chapter 12: Evidence Relevance, Sufficiency, and Reliability

12.1 Criteria for Evidence Quality 12.2 Independence, Corroboration, and the Control Environment 12.3 Evidence an Informed, Competent Person Could Rely On

13 Chapter 13: Technology Options for Findings and Conclusions

13.1 Artificial Intelligence, Machine Learning, and Robotic Process Automation 13.2 Continuous Monitoring, Dashboards, and Embedded Audit Modules

14 Chapter 14: Process Mapping and Data Analytics

14.1 Workflow Segments, Process Maps, Walk-Throughs, and RACI 14.2 Structured vs Unstructured Data and the Analytics Process 14.3 Diagnostic, Prescriptive, Predictive, Anomaly, and Text Analysis

15 Chapter 15: Analytical Review and Finding Evaluation

15.1 Ratios, Variances, Trends, and Benchmarking 15.2 Selecting Analytical Techniques for Engagement Objectives 15.3 Comparing Existing Conditions to Evaluation Criteria 15.4 Root Causes, Effects, and Significance of Findings

16 Chapter 16: Workpapers and Engagement Conclusions

16.1 Organizing Complete Workpapers with Sufficient Evidence 16.2 Linking Workpapers to Results; Retention, Regulation, and Policy 16.3 Aggregating Findings and Concluding on Governance, Risk, and Control

17 Chapter 17: Engagement Supervision

17.1 Supervision Throughout Planning and Fieldwork 17.2 Coordinating Assignments and Reviewing Workpapers and Conclusions 17.3 Evaluating Auditors' Performance

18 Chapter 18: Communication During the Engagement

18.1 Formal and Informal Communication Across Planning, Fieldwork, and Reporting 18.2 Situations That Require Escalation 18.3 Selecting Appropriate Stakeholders for Engagement Communication

19 Chapter 19: Final Review and Test Day

19.1 2025 vs 2019 Traps and Part 2 vs Part 3 Boundaries 19.2 Pacing, Test-Center Rules, and Official Results

4.2 Business Continuity, Disaster Recovery, and Resilience

Key Takeaways Explain This Topic AI

A business impact analysis identifies critical activities and recovery priorities; a business continuity plan is how the business continues; disaster recovery is typically IT restoration — they are not interchangeable labels.

Recovery time objective (RTO) and recovery point objective (RPO) are planning criteria that tell you which processes and which backup designs are in scope for the activity under review.

Un-tested backups are not evidence of recoverability; ask for the last successful restore of the systems that support the activity.

Incident management handles detection, containment, and short-cycle response; disaster recovery is invoked when the disruption exceeds local recovery.

Use the BIA's recovery tiers to decide which continuity controls matter for this engagement; do not turn every Part 2 engagement into an enterprise BCP audit or a Part 3 function-management review.

Last updated: August 2026

Business continuity is in CIA Part 2 as a planning recognition topic (A3d), not as a license to write an enterprise resilience manual. When you plan an engagement of an activity, you recognize business resilience, incident management, business impact analysis (BIA), and backup and recovery testing so you can decide which continuity and recovery controls matter for that activity. You are not sitting Part 3 function-management material, and you are not turning every engagement into an audit of the corporate disaster-recovery program.

BIA, BCP, DR, incident management, and resilience are not synonyms

A business impact analysis identifies which activities are critical, what happens as downtime lengthens (lost revenue, safety, regulatory deadlines, customer harm), which systems, people, and vendors they depend on, and how quickly they must return. The BIA produces recovery priorities plus recovery time and recovery point objectives. It is an analysis, not a playbook.

A business continuity plan is how the business keeps operating: manual workarounds, alternate sites, cross-trained staff, crisis communications, and customer commitments during disruption. Disaster recovery is typically the IT restoration plan: rebuild or failover systems, restore data, and reconnect networks. You can have a BCP workaround (paper receiving logs) while DR is still rebuilding the warehouse system. You can also have restored systems (DR success) while the business still cannot invoice because the BCP never assigned who would catch up the backlog.

Business resilience is the broader capability to absorb shocks, adapt, and recover — including cyber events, facility loss, third-party failure, and people loss. Incident management is the operational process for detecting, classifying, containing, communicating, and closing incidents, often on a scale of hours. Disaster recovery is invoked when the incident or event exceeds local recovery: a data-center loss, successful ransomware encryption of production, or a region-wide outage.

Mixing these on the exam is a gift to the item writer. If the stem is about ranking which processes must return first, the tool is the BIA. If it is about who calls customers and how receiving continues on paper, the tool is the BCP. If it is about restoring the general ledger database, the tool is DR. If it is about the ransomware war room in the first four hours, the tool is incident management.

Concept What it answers Typical owner Planning use

BIA Which activities are critical, and how fast must they return? Business with risk/continuity Sets recovery priorities and RTO/RPO that drive scope

BCP How does the business keep operating during disruption? Activity / continuity Workarounds, staff, communications for this activity

DR How are systems and data restored? IT / infrastructure Recoverability of the systems this activity depends on

Incident management How is an event detected, contained, and closed? IT / operations / cyber Playbooks for outages and cyber events that hit this activity

Resilience Can the organization absorb, adapt, and recover? Enterprise Broader context; do not confuse with one activity's BCP

RTO and RPO as planning criteria

Recovery time objective (RTO) is the maximum acceptable downtime before the impact of an outage becomes intolerable for that activity. Recovery point objective (RPO) is the maximum acceptable data loss, measured in time: an RPO of four hours means backups or replication must be able to restore to a point no older than four hours.

These numbers are planning criteria, not trivia. If payroll's BIA says RTO 24 hours and RPO 4 hours, a weekly backup stored in the same building fails the RPO even if tapes exist, and an untested 72-hour restore runbook fails the RTO. For a treasury payments activity with an RTO of four hours, the engagement risk assessment should treat payment-system recoverability, dual-site processing, and tested failovers as key controls. For a facilities work-order desk with an RTO of 72 hours, the same DR sophistication is not automatically the priority; you would instead ask whether a 72-hour outage is actually acceptable given safety work orders that cannot wait.

The planner compares three things: what the BIA claims, what management's plans and technology can actually deliver, and what the activity under review needs. Mismatches are in-scope risks. An activity labeled Tier 3 in the BIA that in fact feeds a Tier 1 payment process is a dependency gap, not a reason to skip continuity procedures.

Backup existence is not backup recoverability

A3d specifically names backup and recovery testing. Having a backup job in the scheduler is a weak control if restores are never attempted, if backups are not application-consistent, if they sit on the same storage the ransomware encrypts, or if the last successful restore was never documented. Planning questions for the opening interviews:

When was the last restore test for the systems that support this activity?

Was it a full application restore or a file-level sample?

Did the restore meet the RTO, and was the recovered data usable (RPO and integrity)?

Who owns offsite, offline, or immutable copies, and have those copies been restored?

If those answers are vague, recoverability is a high residual risk for any engagement of a time-critical activity. The work program then needs procedures that inspect restore-test evidence, not merely a policy that "backups are taken daily." A screenshot of a backup-job success message is not a restore test.

Incident management versus disaster recovery in the work you plan

Incident management and DR intersect, but they are different control systems. Incident management needs severity definitions, on-call rotations, playbooks (including cyber), communication trees, and criteria for escalation to crisis or DR. DR needs restoration runbooks, failover capability, recovery-environment capacity, and tested data restoration. A payment-system outage that is fixed by restarting a service is an incident. The same outage that requires rebuilding the payment database from backup is a DR event.

For planning a treasury or customer-operations engagement, an untested incident playbook is in scope even if "DR" is owned by infrastructure. You are assessing whether the activity under review can detect and contain events that threaten its objectives. You are not assessing whether the chief audit executive has a seat in the enterprise crisis team — that is function-level governance, not this activity's engagement plan.

Which processes are in scope given recovery priorities

Do not attempt to audit the entire enterprise continuity program inside an engagement of one activity. Use the BIA's tiers. If the activity is Tier 1, continuity and recovery controls are key controls and belong in objectives and scope. If the activity is Tier 3, you still ask whether its dependencies (a Tier 1 payment system, a single vendor, a single administrator) create a hidden criticality the BIA missed. If a "noncritical" activity feeds a critical one, that dependency is a planning finding in the making.

Keep the Part 3 boundary clean. How the internal audit function maintains its own continuity, how often the annual plan covers resilience, and how the CAE reports residual risk on enterprise BCP to the board are not the center of this Part 2 objective. The Organizational Resilience Topical Requirement is issued and becomes effective 30 April 2027; scored CIA items on a new Topical Requirement appear at least six months after the effective date. For the current Part 2 exam, A3d still tests the concepts: BIA, BCP, DR, incident management, and backup testing as planning recognition for the activity under review.

Example recovery time objectives used as engagement planning criteria