Study guide
Business Impact Analysis
CISM Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISM Orientation and 2026 Exam Facts
Current CISM Exam Facts The November 2026 Outline Change The Security Manager Mindset Scaled Score and Preliminary Status Registration Scheduling and Fees Certification After Passing
2 Chapter 2: Information Security Governance
Organizational Culture and Governance Signals Legal, Regulatory, and Contractual Requirements Structures, Roles, and Responsibilities Information Security Strategy Development Governance Frameworks and Standards Strategic Planning, Budgets, and Business Cases
3 Chapter 3: Information Security Risk Management
Emerging Risk and Threat Landscape Vulnerability and Control Deficiency Analysis Risk Assessment and Analysis Risk Treatment and Response Options Risk and Control Ownership Risk Monitoring and Reporting
4 Chapter 4: Information Security Program Development
Program Resources: People, Tools, and Technologies Information Asset Identification and Classification Industry Standards and Frameworks Policies, Procedures, and Guidelines Information Security Program Metrics Program Alignment with Strategy
5 Chapter 5: Program Management and Control Execution
Security Control Design and Selection Control Implementation and Integration Control Testing and Evaluation Security Awareness and Training External Services and Supplier Management Program Communications and Reporting
6 Chapter 6: Incident Management Readiness
Incident Response Plan Business Impact Analysis Business Continuity Plan Disaster Recovery Plan Incident Classification and Categorization Incident Training Testing and Evaluation
7 Chapter 7: Incident Management Operations
Incident Management Tools and Techniques Incident Investigation and Evaluation Incident Containment Methods Incident Response Communications Incident Eradication and Recovery Post-Incident Review Practices
8 Chapter 8: Supporting Governance Tasks
Internal and External Influences Maintaining Security Strategy Governance Framework Maintenance Corporate Governance Integration Policy Direction and Standards Business Cases for Security Investment
9 Chapter 9: Cross-Domain Risk and Program Decisions
Senior Leadership Commitment Responsibilities and Lines of Authority Program Effectiveness Reporting Risk Process Oversight Threat and Vulnerability Participation Risk Appetite and Treatment Decisions
10 Chapter 10: External Parties Data and Emerging Technology
Information Security Requirements in Contracts Monitoring External Parties Information Asset Lifecycle Thinking Cloud SaaS and Provider Risk AI, Blockchain, and Ransomware Context Compliance and Control Evidence
11 Chapter 11: CISM Practice Strategy
Domain-Weighted Study Allocation Management-Focused Answer Choices One-Best-Answer Elimination Timed Four-Hour Practice Using Domain Feedback Correctly Retake, Rescore, and Post-Exam Feedback
12 Chapter 12: Final Review and Exam Day Readiness
Two-Week Final Review Plan Exam Day Rules and Identification Remote Proctoring Readiness Preliminary Status Versus Official Score Application Window, Experience, and Ethics CPE Maintenance After Certification
Business Impact Analysis
Key Takeaways Explain This Topic AI
The BIA identifies critical business processes, quantifies the impact of disruption over time, and produces the recovery objectives (RTO, RPO, MTO/MTD) that drive BCP and DRP.
RTO is allowable downtime; RPO is allowable data loss measured backward from the disruption; MTD/MTO is the absolute survival limit and must be greater than or equal to RTO.
Recovery objectives are business decisions owned by process owners and senior management, not IT preferences.
The BIA is the foundation: without it, recovery investments cannot be prioritized or defended to management.
Last updated: June 2026
Purpose of the Business Impact Analysis
The Business Impact Analysis (BIA) identifies the organization's critical business processes, estimates the operational and financial impact of their disruption over time, and establishes the recovery objectives that the Business Continuity Plan (BCP) and Disaster Recovery Plan (DRP) must meet. On CISM, the BIA is the foundation of all continuity work: you cannot rationally decide how fast to recover, how much redundancy to buy, or what to fund first without it.
A BIA answers three management questions. First, which processes, if interrupted, threaten the enterprise? Second, how does the impact escalate the longer the process is down (impact is rarely linear, it accelerates)? Third, what dependencies, applications, data, staff, suppliers, must be restored to bring each process back? The output is a prioritized list with defensible numbers, not opinion.
Recovery Objectives the BIA Produces
These metrics appear constantly on the exam. Know the definition and the directional relationships.
- Metric Definition Reads as
- RTO (Recovery Time Objective) Maximum acceptable downtime before recovery "How long can we be down?"
- RPO (Recovery Point Objective) Maximum acceptable data loss, measured backward "How much data can we lose?"
- MTD / MTO Maximum tolerable downtime / outage before the business is threatened "The absolute limit"
SDO (Service Delivery Objective) Service level required while running in alternate mode "How well must the workaround perform?"
AIW (Acceptable Interruption Window) Time the org can tolerate before impact is unacceptable "Window before pain"
The key relationship: MTD (or MTO) must be greater than or equal to RTO . RTO is set inside the tolerable limit; if RTO exceeds MTD, the recovery plan fails by design. RPO drives backup frequency: a one-hour RPO requires backups or replication at least hourly.
Conducting and Using the BIA
A BIA is performed with the business process owners , not by IT in isolation, because only the business can say what an outage truly costs in revenue, penalties, reputation, safety, and contractual breach. The information security manager facilitates the analysis, validates assumptions, and translates results into recovery requirements that vendors and engineers can build to.
Worked RPO/RTO example
An order-entry system processes 500 transactions per hour worth roughly 100,000 USD. Management sets RTO = 2 hours (it can survive two hours offline) and RPO = 15 minutes (it can afford to lose at most 15 minutes of orders). The DRP must therefore restore the application within two hours and replicate transaction data at least every 15 minutes. If the BIA later shows MTD is only 90 minutes, the 2-hour RTO is invalid and must be tightened, because RTO cannot exceed MTD.
Common CISM Traps
Confusing RTO and RPO: RTO is about time to restore ; RPO is about data currency . They are independent and often different numbers.
Letting IT set objectives: Recovery objectives are business decisions ; an answer where process owners and senior management own them is stronger.
Skipping the BIA: Buying a hot site or backup tooling before the BIA is putting controls ahead of requirements, ISACA penalizes solutions chosen without a documented need.
Treating impact as linear: Impact typically accelerates with outage duration, which is why short RTOs cost disproportionately more.
The BIA is also the document a security manager uses to justify budget to the board: it converts "we should have a DR site" into "a four-hour outage of process X costs 400,000 USD, so a recovery investment of Y is defensible."
How a BIA Is Performed, Step by Step
A defensible BIA follows a repeatable method, and exam questions sometimes test whether a step was skipped or done out of order:
Identify business processes , not just systems. Map each process to the applications, data, people, facilities, and suppliers it depends on.
Gather impact data from process owners through interviews, questionnaires, and workshops. Capture financial loss, regulatory penalties, contractual breach, reputational harm, and safety consequences.
Determine how impact escalates over time , building an impact-over-duration curve for each process. This reveals the point where consequences become unacceptable.
Set recovery objectives (RTO, RPO, MTD, SDO) with the business, validated by senior management.
Prioritize processes by criticality so recovery investment and sequencing follow the numbers.
Document and obtain sign-off , then schedule periodic review as the business changes.
Impact Categories the Exam Expects
A BIA quantifies more than lost revenue. ISACA expects a broad view of consequences:
- Financial: lost sales, idle labor, recovery costs, penalties
- Regulatory and legal: fines, breach-notification obligations, litigation
- Operational: inability to deliver products or services
- Reputational: customer attrition, brand damage, loss of investor confidence
- Health and safety: harm to people where systems support physical operations
- Connecting the BIA to Risk and Continuity
The BIA is distinct from a risk assessment : a risk assessment estimates the likelihood and impact of specific threats, while the BIA assumes a disruption has occurred and measures what it costs over time . Both inform planning, but they answer different questions, a common distractor confuses the two. The BIA's outputs flow directly into the BCP (which processes to resume first) and the DRP (how fast and to what data currency to recover systems).
Without a current BIA, every downstream recovery decision rests on opinion, and ISACA consistently rewards the answer that grounds continuity choices in documented business impact rather than technical preference or vendor recommendation. Re-running or refreshing the BIA after major change, mergers, new product lines, large system migrations, is therefore a maintenance obligation, not a one-time project.