Study guide

Strategic Planning, Budgets, and Business Cases

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

Strategic Planning, Budgets, and Business Cases

Key Takeaways Explain This Topic AI

A business case justifies security investment in business terms — cost, risk reduction, and benefit — not in technical language.

ROSI (Return on Security Investment) uses ALE before and after a control minus the control's cost to express value to executives.

ALE = SLE x ARO; SLE = Asset Value x Exposure Factor — the core quantitative formulas behind cost-justified security spending.

Metrics for the board should be business- and risk-aligned KGIs/KPIs, not raw technical counts like 'number of blocked packets.'

Last updated: June 2026

The Business Case: Speaking the Board's Language

Security initiatives compete with every other corporate investment, so CISM expects a manager to justify spending with a business case stated in business terms: the cost of the initiative, the risk it reduces , the benefits, and the alternatives considered. A business case that argues from fear or technical detail ("we will be hacked," "we need next-gen tooling") loses to one that argues from quantified risk reduction and alignment with business objectives. The strongest business cases tie directly to objectives the board already cares about — revenue protection, regulatory standing, customer trust.

Quantifying Value: ALE and ROSI

The quantitative core the exam tests is the annualized loss expectancy chain:

Single Loss Expectancy (SLE) = Asset Value x Exposure Factor (EF) (the fraction of the asset lost per event).

Annualized Rate of Occurrence (ARO) = expected events per year.

Annualized Loss Expectancy (ALE) = SLE x ARO.

Return on Security Investment (ROSI) then expresses control value:

ROSI = (ALE before control - ALE after control - annual cost of control) / annual cost of control

  • Term Formula Example
  • SLE Asset Value x EF $500,000 x 0.4 = $200,000
  • ALE SLE x ARO $200,000 x 0.5 = $100,000
  • ALE after control reduced SLE/ARO drops to $20,000
  • ROSI (100,000 - 20,000 - 30,000) / 30,000 ~1.67, i.e., 167% return

Worked example: a $30,000/year control that cuts ALE from $100,000 to $20,000 avoids $80,000 of expected loss for $30,000, a strong positive return. The exam reasoning point: if the annual cost of a control exceeds the loss it prevents, the control is not cost-justified — accepting or transferring the risk may be the better governed decision. A control should not cost more than the asset or risk it protects.

Budgeting as Risk Treatment

A security budget is a risk-treatment portfolio , not a fixed percentage of IT spend. The manager allocates funds to the initiatives that reduce the most risk per dollar toward the board's appetite, and explicitly identifies risks being accepted (no spend) because treatment would cost more than the exposure. When a budget is cut, the governed response is to re-prioritize and re-present the residual risk to management for acceptance — not to silently leave controls unfunded. Management owns the decision to accept the increased risk.

Metrics the Board Can Use

Reporting closes the governance loop. CISM distinguishes:

Key Goal Indicators (KGIs) — did we achieve the objective? (e.g., "100% of critical systems patched within SLA").

Key Performance Indicators (KPIs) — how well is the process performing toward the goal? (e.g., "mean time to patch").

Key Risk Indicators (KRIs) — early-warning signals that risk is rising.

The trap is reporting raw technical counts — blocked packets, alerts triaged — to executives. Those are operational noise at board level. Board metrics must connect to business outcomes and risk posture , expressed in trends and against appetite, so leaders can make funding and risk-acceptance decisions. Effective metrics are relevant, quantifiable, reliable, and tied to a decision someone will actually make.

Qualitative Versus Quantitative Justification

Not every business case can produce clean dollar figures, and CISM expects you to know when each approach fits. Quantitative analysis (SLE, ALE, ROSI) gives executives comparable numbers and works when loss data and frequencies are estimable. Qualitative analysis (high/medium/low impact and likelihood) fits novel or hard-to-quantify risks — reputational harm, regulatory censure — where invented precision would mislead. Mature programs combine them: qualitative screening to rank, then quantitative depth on the top risks.

A trap answer insists on a precise ALE for a risk with no historical data; the better answer acknowledges the uncertainty and supports the decision qualitatively while gathering data.

  • Approach Best when Output
  • Quantitative Loss and frequency are estimable ALE, ROSI, payback in currency
  • Qualitative Data is scarce or impact is intangible Ranked high/medium/low ratings
  • Hybrid Most real programs Qualitative triage, quantitative deep-dive
  • Total Cost, Capex, and the Funding Conversation

A credible budget reflects the total cost of ownership (TCO) of a control, not just its purchase price: licensing, implementation, staffing, training, maintenance, and eventual decommissioning. A tool that is cheap to buy but requires two new analysts to operate may have a worse ROSI than a pricier but automated alternative. Managers also distinguish capital expenditure (capex) — one-time investment, often depreciated — from operating expenditure (opex) — recurring cost — because the distinction affects how finance and the board evaluate the request.

When funding is insufficient to treat all risks, the manager presents a prioritized portfolio showing risk reduced per dollar and explicitly lists the risks that will be accepted if a given tranche is not funded. This converts the budget conversation into a governed risk-acceptance decision the board owns, rather than an open-ended request. The recurring exam point: management, not the security manager, accepts residual risk , and the manager's job is to make that acceptance informed, documented, and revisited.

A business case, a defensible cost-benefit analysis, and risk-aligned metrics together close the governance loop that Domain 1 opens — direction is set, resources are justified in business terms, and performance is reported back to the accountable layer.