The CISM blueprint is split across 4 domains. Weights are the official share of the exam; see the official exam guide for the authoritative breakdown.
What you must be able to do. Read a governance scenario and pick the step that aligns security to a business objective, set through the right structure, role, or framework, and justified to a board in risk-and-return terms.
In one sentenceSetting direction from the top: culture and tone, the legal and regulatory drivers, the roles and structures, and a security strategy aligned to the business and funded by a business case.
Recall check: answer these from memory first
- What must a security strategy align to first, and who owns the decision that it does?
- Say in one sentence what COBIT, ISO/IEC 27001 and the NIST CSF are each for.
- How would you justify a security investment to a board: in technical terms or in risk and return?
What it tests. Whether you can set the direction for security from the top: organisational culture and tone at the top, the legal, regulatory and contractual requirements that shape the framework, and the structures, roles and responsibilities such as the CISO role, a steering committee and segregation of duties. It also covers developing a security strategy aligned to business objectives, applying governance frameworks such as COBIT, ISO/IEC 27001 and the NIST CSF, and strategic planning including budgets and business cases.
How to study it. Anchor everything to alignment: governance exists to make security serve business objectives, so for any scenario ask what the business is trying to achieve before you reason about controls. Learn the frameworks by purpose rather than clause numbers, so you can say in a sentence what COBIT, ISO/IEC 27001 and the NIST CSF are each for. Be ready to justify a security investment as a business case to a board that thinks in risk and return, not in technical detail.
Easy to confuse
- Governance versus management. Governance sets direction, accountability, and the risk appetite from the top, usually the board and steering committee; management runs the programme inside those bounds. If the scenario asks who sets or approves direction it is governance; if it asks who executes it is management.
- Strategy versus governance framework. The strategy is where security is going and why, tied to business goals; a framework such as COBIT or ISO/IEC 27001 is the structured method you adopt to get there. The exam tests strategy as the destination and the framework as the chosen vehicle.
- Aligned to business objectives versus most secure option. The CISM answer is the one that supports the stated business objective at an acceptable risk, not the one that maximises security. An option that is more secure but ignores cost, the objective, or the agreed appetite is the distractor.
Worked example from the CISM bank
lock_openFree sampleInformation Security Governancehard
Midway through the financial year, an unforeseen regulatory change forces the information security manager to fund an urgent data-protection project that was not in the approved budget. The annual security budget is already fully committed and the board has frozen requests for additional funds until the next cycle. Which action best reflects sound resource allocation in this situation?
- ADefer the regulatory project to the next budget cycle and formally document the resulting compliance exposure as an accepted risk.
- BRe-prioritise the existing portfolio and reallocate funds from lower-risk initiatives to the regulatory project after assessing the impact.check_circle Correct
- CReduce the scope of every active initiative by an equal percentage to free the funds the regulatory project needs.
- DFund the regulatory project from operational contingency without informing the board until the year-end budget review.
Under a frozen budget, sound resource allocation re-prioritises committed funds toward the highest risk based on an impact assessment. Resource management means continuously steering finite funds toward the greatest risk reduction. Reallocating from lower-risk initiatives, supported by an impact assessment, meets the regulatory obligation without breaching governance, whereas deferral accepts an avoidable breach, equal cuts ignore relative risk, and drawing contingency in secret bypasses board oversight.
Why A is wrong: Tempting because it respects the funding freeze and uses formal risk acceptance, but accepting a known regulatory breach when reallocation is possible is poor stewardship and the manager rarely has authority to accept that level of risk alone.
Why B is correct: Correct because re-prioritising within the committed budget directs scarce resources to the highest-risk obligation while a documented impact assessment keeps the deferred work visible, which is disciplined resource management under constraint.
Why C is wrong: Tempting because spreading the cut feels even-handed, but uniform reductions ignore the relative risk of each initiative and can weaken high-value controls, which is the opposite of risk-based allocation.
Why D is wrong: Tempting because contingency exists for surprises, but quietly drawing it down and bypassing governance for a material regulatory matter breaches transparency and undermines the board's oversight of the budget.
What you must be able to do. Given a risk scenario, assess it against the organisation's appetite and pick the treatment a manager would choose, with the right owner accountable for what remains.
In one sentenceIdentifying, assessing and treating risk to the agreed appetite, with the quantitative basics, clear ownership of residual risk, and reporting through key risk indicators.
Recall check: answer these from memory first
- Name the four risk treatment options and the one factor that decides between them.
- Write the SLE and ALE formulae, then compute the ALE for an asset worth 40,000 with a 25 percent exposure factor that is hit twice a year.
- Who accepts residual risk: the security manager or the business owner, and what is security's role instead?
What it tests. How you identify, assess and respond to risk: the emerging threat landscape, vulnerability and control deficiency analysis, and risk assessment using both qualitative and quantitative methods including the ALE and SLE calculations. It then tests choosing risk treatment options against the organisation's risk appetite, establishing risk and control ownership so residual risk is accountable, and monitoring and reporting risk to stakeholders through key risk indicators.
How to study it. Make risk appetite the lens for every treatment decision: you accept, mitigate, transfer or avoid based on what the organisation has agreed to tolerate, and the business owns that decision, not security. Learn the quantitative basics cold, including single loss expectancy, annual rate of occurrence and annualised loss expectancy, because a handful of questions turn on them. Keep ownership clear in your head: the asset or business owner accepts residual risk, security advises and reports.
Easy to confuse
- Risk appetite versus risk tolerance. Appetite is how much risk the organisation is willing to take overall to pursue its objectives; tolerance is the acceptable variation around a specific risk. Appetite is the strategic boundary set at the top; tolerance is the practical limit on one item.
- Inherent risk versus residual risk. Inherent risk is the exposure before any control; residual risk is what remains after the chosen treatment. The exam tests that you treat down to residual and that a business owner, not security, accepts whatever residual is left.
- Risk mitigation versus risk transfer. Mitigation reduces the likelihood or impact with a control you implement; transfer shifts the financial consequence to a third party, classically insurance or a contract clause. Transfer moves the cost of the loss, it does not remove the risk event.
Worked example from the CISM bank
lock_openFree sampleInformation Security Risk Managementhard
An information security manager is preparing a risk assessment for a newly launched product that has no internal incident history, no comparable industry loss data and a fast-changing threat landscape. The board wants a defensible prioritisation of risks within two weeks. Which analysis approach should the manager adopt first, and why?
- AA quantitative analysis, because expressing every risk in annual loss expectancy gives the board the precise monetary ranking it expects.
- BA quantitative Monte Carlo simulation, because modelling thousands of loss iterations compensates for the absence of historical data.
- CA qualitative analysis, because expert-judgement ratings of likelihood and impact can prioritise risks quickly when reliable loss frequency data is unavailable.check_circle Correct
- DA deferral of any analysis, because no prioritisation can be defended until at least twelve months of incident data has accumulated.
Select qualitative analysis when reliable frequency and loss data are absent and a rapid, defensible prioritisation of risks is required. Quantitative methods depend on credible occurrence and impact data to avoid false precision, so when such data is unavailable and time is short, structured qualitative ratings of likelihood and impact give a defensible first-pass prioritisation that can be refined quantitatively as data matures.
Why A is wrong: This is tempting because monetary figures look authoritative, but without occurrence and loss data the annual loss expectancy values would rest on guessed inputs, producing false precision rather than a defensible ranking.
Why B is wrong: Monte Carlo simulation still needs credible input distributions drawn from data or calibrated estimates; running it on unfounded assumptions multiplies uncertainty rather than removing it, and it is unlikely to be defensible in two weeks.
Why C is correct: With no historical or industry frequency data and a short deadline, qualitative analysis lets subject-matter experts rank scenarios using structured likelihood and impact scales, which is the appropriate first step when the inputs for credible quantification do not yet exist.
Why D is wrong: Waiting for data leaves the new product unmanaged during its most exposed period; the manager can and should prioritise risks now using qualitative methods rather than declining to assess at all.
What you must be able to do. In a programme scenario, choose the document, control, or metric a manager would use, tying each control back to the risk it addresses rather than to the technology.
In one sentenceBuilding and running the programme, the largest domain: resources, asset classification, the policy hierarchy, control selection and testing, awareness, third-party risk, and reporting.
Recall check: answer these from memory first
- Put these in hierarchy order and say which one is mandatory: standard, policy, procedure, guideline.
- What should drive the selection of any control: the available technology or the risk it addresses?
- What is fourth-party risk, and why does managing third parties not fully cover it?
What it tests. Building and running the programme itself, and this is the largest domain by weight: managing programme resources, classifying information assets to set protection requirements, applying standards such as ISO/IEC 27002 and NIST SP 800-53, and writing the policy, standard, procedure and guideline hierarchy. It also covers programme metrics, designing and selecting controls for identified risks, implementing and integrating them with defence in depth, testing control effectiveness, running awareness and training, managing third- and fourth-party risk, and reporting programme status to stakeholders.
How to study it. Spend the most time here because it carries the most marks. Get the document hierarchy exact: policy sets intent, standards are mandatory, procedures are step-by-step, guidelines are advisory, and questions trade on confusing them. Learn controls by what they do in time, preventive before the event and detective during or after, and tie control selection back to the risk it addresses rather than to the technology. Treat third-party and supply-chain risk as a first-class topic, including fourth parties your suppliers depend on.
Easy to confuse
- Policy versus standard versus procedure versus guideline. A policy is the high-level intent (we protect customer data), a standard is the mandatory specific (use AES-256), a procedure is the step-by-step how, and a guideline is advisory not enforced. The exam tests which document a given statement belongs in, and that only the guideline is optional.
- Preventive versus detective control. A preventive control stops an event before it happens (access control, encryption); a detective control identifies it during or after (logging, monitoring, audit). The trap is offering a strong detective control when the scenario needs prevention, or the reverse.
- Third-party versus fourth-party risk. Third-party risk is the risk from your direct suppliers; fourth-party risk is the risk from their suppliers, which you do not contract with but still depend on. The exam tests that vendor assessment must reach beyond the direct relationship.
Worked example from the CISM bank
lock_openFree sampleInformation Security Programeasy
A retailer is building its first data classification scheme. The information security manager must decide what should drive the sensitivity level assigned to each information asset. Which factor should primarily determine the classification level?
- AThe potential business impact if the asset's confidentiality, integrity, or availability were compromisedcheck_circle Correct
- BThe storage format of the asset, such as whether it is held in a database, a spreadsheet, or a paper file
- CThe number of staff who currently request access to the asset during normal operations
- DThe age of the asset and how long it has been retained in the records management system
Information asset classification should be driven by the business impact of a loss of confidentiality, integrity, or availability. Classification expresses the worth of information to the organisation, and that worth is judged by the consequences to the business if the asset is disclosed, altered, or lost, which is why impact is the primary driver rather than format, demand, or age.
Why A is correct: Correct because classification reflects the value and sensitivity of the information, which is measured by the harm to the business if it were disclosed, altered, or made unavailable.
Why B is wrong: Tempting because storage format does affect some control choices, but format is a handling consideration that follows classification; it does not define how sensitive the information itself is.
Why C is wrong: Tempting because high demand can suggest importance, but access volume reflects operational convenience, not the inherent sensitivity that classification is meant to capture.
Why D is wrong: Tempting because retention schedules relate to data governance, but age alone does not set sensitivity; old records can be highly sensitive and new ones trivial.
What you must be able to do. Place an incident scenario at the correct lifecycle step and choose the next action a manager would take, in order, with recovery objectives set by the business impact analysis.
In one sentencePreparing for and running incident response, the second-largest domain: the lifecycle in order, BIA-driven RTO and RPO, the BCP and DRP, forensics and chain of custody, and the post-incident review.
Recall check: answer these from memory first
- List the incident lifecycle phases in order, and say which phase isolating an infected host belongs to.
- Define RTO and RPO in one line each, and name the analysis that sets both.
- Which comes first in a response, containment or eradication, and why is the other order a trap?
What it tests. Preparing for and running the response to incidents, the second-largest domain: maintaining an incident response plan aligned to the business continuity and disaster recovery plans, conducting a business impact analysis to set recovery priorities with RTO and RPO, and developing the BCP and DRP. It then covers incident classification and triage, training and tabletop testing, detection and response tooling such as SIEM and SOAR, investigation and forensics including chain of custody, containment, communications and regulatory notification, eradication and recovery, and the post-incident review.
How to study it. Learn the lifecycle as an ordered flow and resist jumping ahead: preparation, detection, triage and classification, containment, eradication, recovery, then the post-incident review. A common trap is choosing eradication before containment, so fix the order in your mind. Keep the recovery objectives precise: RTO is how fast you must be back, RPO is how much data you can afford to lose, and the business impact analysis sets both. Know that containment limits scope, eradication removes the cause, and the review feeds lessons learned back into the programme.
Easy to confuse
- Containment versus eradication. Containment limits the scope and stops the incident spreading (isolate the host); eradication removes the root cause (delete the malware, close the hole). Containment always comes first, and choosing eradication while the incident is still spreading is the classic trap.
- RTO versus RPO. RTO is the maximum acceptable time to restore a service; RPO is the maximum data loss you can accept, measured backwards from the outage. RTO drives recovery speed and failover; RPO drives backup frequency, and both come from the business impact analysis.
- BCP versus DRP. The business continuity plan keeps critical business operations running during a disruption, across people and processes; the disaster recovery plan restores the IT systems and data that underpin them. The DRP is the technical subset; the BCP is the wider business response.
Worked example from the CISM bank
lock_openFree sampleIncident Managementmedium
An organisation operating in a jurisdiction with a mandatory data breach notification regime has confirmed that personal data has been exfiltrated and that the breach is likely to result in serious harm to affected individuals. The information security manager is deciding what most strongly determines the deadline by which the supervisory authority must be notified. Which factor is the primary driver of that deadline?
- AThe date on which technical containment of the affected systems was fully completed by the response team.
- BThe point at which the organisation became aware, or reasonably should have become aware, that a notifiable breach had occurred.check_circle Correct
- CThe date on which the board of directors formally reviews and signs off the incident response report.
- DThe date on which the organisation finishes calculating the total financial cost of the incident for insurance purposes.
Mandatory breach notification deadlines to regulators are generally driven by when the organisation became aware of a notifiable breach. Statutory breach regimes set notification timeframes running from the organisation's knowledge, or reasonable means of knowledge, of a notifiable breach; awareness, not containment or internal governance, is what triggers and bounds the regulatory clock.
Why A is wrong: Tempting because containment is an important operational milestone, but notification obligations are tied to awareness of the breach rather than to completing technical remediation, which may come much later.
Why B is correct: Correct because mandatory breach regimes generally start the regulatory notification clock from the organisation's awareness of a notifiable breach, making the date of awareness the key driver of the statutory deadline.
Why C is wrong: Tempting because senior approval feels procedurally necessary, but a board review schedule is internal and cannot lawfully delay a statutory notification deadline driven by awareness.
Why D is wrong: Tempting because insurers and cost data matter for recovery, but financial quantification is unrelated to the regulatory deadline, which is anchored to awareness of a notifiable breach.