The CRISC 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. Given a scenario about strategy, structure, culture, policy, law or appetite, choose the action that aligns IT risk management with business objectives and places accountability with the right owner under a sound risk framework.
In one sentenceThe foundation layer: making IT risk management serve business strategy through clear ownership, appetite, policy and a framework, not technical activity for its own sake.
Recall check: answer these from memory first
- What is the strongest evidence that IT risk management is aligned with strategy: deriving appetite and treatment priorities from approved objectives, or counting closed risk scenarios?
- Under the three lines of defence, who owns the risk, who provides oversight, and who gives independent assurance?
- A regulator keeps amending guidance and the changes are only noticed when an auditor cites them months later. What practice most reliably keeps the programme aligned?
- Under the ISACA Code of Professional Ethics, what must a practitioner do first when asked to assess a vendor where a close relative is a senior executive?
What it tests. Whether you can ground the whole risk programme in business intent. Aligning the IT risk approach with organisational strategy, goals and objectives; defining structures, roles and the three lines of defence that separate ownership, oversight and independent assurance; reading how organisational culture shapes risk-aware behaviour; using policies and standards as the instruments that turn governance intent into operational control; identifying legal, regulatory and contractual obligations; building business resilience and continuity into governance; applying enterprise risk management and a risk management framework; setting risk appetite and tolerance to guide decisions; maintaining the enterprise risk profile; and applying the ISACA Code of Professional Ethics, including disclosing conflicts of interest.
How to study it. Anchor everything to one idea: the strategy drives the risk decisions, not the other way round. Practise reading a scenario and asking what the approved objectives, appetite and tolerance imply, then pick the option that derives from them. Learn the three lines of defence cold, because the exam uses them to test who should own, oversee and independently assure a risk, and the wrong answers blur those roles. Treat policies and standards as the bridge from intent to control, and regulatory alignment as a continuous, owned horizon-scanning activity rather than a one-time mapping or a lagging audit. For ethics, drill the reflex that a conflict of interest is disclosed to the right stakeholders first, before any work proceeds.
Easy to confuse
- Risk appetite versus risk tolerance. Appetite is the broad amount and type of risk the organisation is willing to pursue toward its objectives; tolerance is the acceptable variation around a specific objective or metric. Appetite sets the overall stance, tolerance sets the measurable threshold that triggers action.
- Strategic alignment versus operational coverage. Alignment means business objectives drive appetite, tolerance and treatment priorities so intent is the controlling input; coverage means mapping every scenario to an objective or closing findings on schedule. The exam treats deriving decisions from strategy as alignment, and counting activity as a distractor.
- Policy versus standard. A policy states management intent and the mandatory direction, while a standard specifies the measurable, enforceable requirements that make the policy operational. Policy is the why and the must, the standard is the how-much that translates it into control.
Worked example from the CRISC bank
lock_openFree sampleGovernancemedium
A risk practitioner is asked to demonstrate that the IT risk management approach supports the organisation's strategy. Which action provides the strongest evidence of strategic alignment?
- ADeriving risk appetite, tolerance and treatment priorities directly from the approved strategic objectivescheck_circle Correct
- BMapping each identified IT risk scenario to the specific business objectives it could impair
- CCounting how many IT risk scenarios were closed within the agreed remediation window
- DPublishing the IT risk register to every department head on a fixed monthly schedule
Strategic alignment is proven when risk appetite, tolerance and treatment priorities are derived from approved strategic objectives. Alignment means the strategy drives the risk decisions, so deriving appetite, tolerance and treatment priorities from the approved objectives makes business intent the controlling input rather than an afterthought layered onto technical activity.
Why A is correct: When appetite, tolerance and priorities flow from the approved strategic objectives, the risk approach is demonstrably governed by strategy rather than run as an isolated technical exercise.
Why B is wrong: Mapping risks to objectives is useful and tempting because it shows traceability, but it documents exposure rather than proving the overall approach is steered by strategy.
Why C is wrong: Closure rates measure operational efficiency of treatment, so they look like progress, yet they say nothing about whether the work served the organisation's strategic goals.
Why D is wrong: Wide distribution improves transparency and feels like good governance, but circulating a register does not show that risk decisions are anchored to business strategy.
What you must be able to do. Given a scenario with a threat, an asset, emerging technology or a control gap, build a usable risk scenario and analyse likelihood and impact correctly, distinguishing inherent from residual risk by how effectively controls actually operate.
In one sentenceThe sizing layer: turning events, assets and consequences into analysable risk scenarios and estimating likelihood and impact before any treatment is chosen.
Recall check: answer these from memory first
- What four components make an IT risk scenario usable for analysis and response?
- Two systems share the same inherent rating but very different residual risk. What single factor explains the difference?
- When an AI model scores loan applications, what is the primary fairness risk to assess, and why?
- Which exposure is specific to a large language model rather than to document handling in general?
What it tests. Whether you can understand a risk before deciding what to do about it. Developing IT risk scenarios from a threat actor, an event, an affected asset and a loss consequence; analysing the threat landscape and applying threat modelling; conducting vulnerability and control deficiency analysis; identifying risk from emerging technologies including artificial intelligence, large language models and quantum computing; selecting appropriate assessment concepts, standards and frameworks; performing qualitative and quantitative analysis to estimate likelihood and impact; and distinguishing inherent from residual risk, using business impact analysis to evaluate risk against criteria.
How to study it. Drill the four-part anatomy of a risk scenario until it is automatic: threat actor, event, affected asset, business loss consequence. The exam repeatedly offers tempting but wrong answers that are really inventories (a control list, a network diagram, past audit findings) rather than scenarios, so learn to reject anything that does not connect cause to business consequence. Lock the inherent-versus-residual distinction by reasoning from control operating effectiveness: identical inherent ratings produce different residual risk when one system's controls are bypassed. For emerging tech, learn the model-specific exposures: training-data bias as the fairness risk, and fluent fabricated output (hallucination) as the risk unique to large language models, distinct from generic data-handling issues.
Easy to confuse
- Inherent risk versus residual risk. Inherent risk is the gross exposure before controls; residual risk is what remains after controls operate, and it varies with how effectively those controls actually work. Identical inherent ratings can leave very different residual risk when one set of controls is weak or bypassed.
- A risk scenario versus a control inventory. A risk scenario binds a threat actor, an event, an affected asset and a loss consequence so likelihood and impact can be estimated; a control list, network diagram or audit-finding summary describes the environment but supplies none of those four elements. Only the scenario is analysable.
- LLM hallucination versus generic data-handling risk. Hallucination is the model presenting fabricated or unsupported statements as confident fact, a risk unique to the model; transport encryption, access control and performance are document-workflow risks that apply to any process. The model-specific exposure is the unsupported output staff may act on.
Worked example from the CRISC bank
lock_openFree sampleRisk Assessmenthard
Two systems share an identical inherent risk rating. System One operates behind mature, tested controls, while System Two relies on controls that monitoring shows are frequently bypassed. A practitioner is explaining to an auditor why the two systems carry very different residual risk despite the same inherent rating. Which explanation is correct?
- AResidual risk differs because each system was assigned a different inherent rating once the asset values were recalculated for the audit.
- BResidual risk differs because only System One has been formally evaluated against the organisation's documented risk acceptance criteria so far.
- CResidual risk differs because System Two has a higher inherent likelihood once its threat environment is reassessed against current intelligence.
- DResidual risk differs because the effectiveness of the operating controls differs, and weak or bypassed controls leave more exposure remaining.check_circle Correct
Explain that residual risk varies with the operating effectiveness of controls even when inherent risk ratings are identical. Inherent risk is the same gross exposure before controls, while residual risk reflects how effectively controls actually operate; bypassed or weak controls remove less exposure, so an identical inherent rating can yield very different residual risk.
Why A is wrong: This is tempting because asset value drives inherent risk, but the scenario fixes both inherent ratings as identical, so a recalculated inherent value cannot be the reason.
Why B is wrong: This is plausible because evaluation order matters administratively, but the timing of an acceptance review does not change the residual risk that each system actually carries.
Why C is wrong: This is attractive because likelihood feeds risk, but altering inherent likelihood contradicts the stated identical inherent rating, so it does not explain the residual gap.
Why D is correct: Residual risk is what remains after controls operate, so the system whose controls are frequently bypassed retains more exposure even though its inherent rating matches the other.
What you must be able to do. Given an assessed risk, choose the treatment that fits appetite and cost, assign ownership and proportionate controls, test their effectiveness, and report status to the right audience using the right metrics.
In one sentenceThe heaviest domain: choosing the right response within appetite and cost, owning it, controlling it proportionately, and reporting it to the audience that must act on it.
Recall check: answer these from memory first
- Residual risk sits just above appetite and further controls would cost more than the potential loss. Which treatment, and what must accompany it?
- Which treatment fits a low-likelihood high-impact risk where the proposed safeguard costs more per year than the largest plausible single loss?
- What changes when you tailor the same risk data from an operational control report into a board report?
- An organisation wants a detailed, prescriptive catalogue of security and privacy controls with selectable baselines. Which type of framework fits?
What it tests. The core of the exam, deciding what to do and telling the right people. Selecting risk treatment and response options consistent with appetite; developing treatment plans with actions, resources and timelines; establishing risk and control ownership so accountability is clear; managing third-party, supply-chain and fourth-party risk across the vendor lifecycle; classifying control types and applying control standards and frameworks; designing and selecting controls proportionate to exposure and cost of control; implementing and integrating controls; testing controls and evaluating effectiveness; monitoring risk and controls and managing issues, findings and exceptions; and reporting status to stakeholders using KPIs, KRIs and KCIs with appropriate visualisations.
How to study it. This is the largest domain by weight, so spend the most time here. Fix the four treatment options and when each applies: accept (with informed owner sign-off) when the cost of further control exceeds the loss, mitigate when residual sits above appetite and control is proportionate, transfer when a third party can carry the financial impact, avoid when the activity itself should be retired. Make cost-benefit a reflex: never recommend a control that costs more each year than the largest plausible loss it prevents. Learn the metric families precisely (KPI for performance, KRI for emerging exposure, KCI for control health) and practise tailoring the same data into a board report, which aggregates exposure against appetite and surfaces decisions, versus an operational report full of detail. Distinguish framework types so you can match a stated need to a control catalogue, a governance framework, a maturity model or an assessment method.
Easy to confuse
- Risk acceptance versus risk transfer. Acceptance keeps the exposure with documented, informed owner sign-off when further treatment costs more than the loss; transfer shifts the financial impact to a third party such as an insurer while the underlying risk often remains. Acceptance owns the residual, transfer pays someone else to absorb part of the impact.
- KRI versus KPI versus KCI. A KRI signals changing risk exposure and warns before a threshold is breached, a KPI measures whether an objective or process is performing, and a KCI measures whether a control is operating effectively. Match the metric to whether you are tracking risk, performance or control health.
- Control catalogue framework versus governance framework. A control catalogue enumerates detailed, prescriptive security and privacy controls in selectable baselines you map to systems; a governance framework defines objectives and management practices but leaves specific control selection to you. Pick the catalogue when the need is prescriptive, ready-to-map controls.
Worked example from the CRISC bank
lock_openFree sampleRisk Response and Reportingmedium
A residual risk sits just above the organisation's stated risk appetite, and the cost of further controls would clearly exceed the potential loss. The business owner is willing to live with the exposure. Which risk treatment should the practitioner recommend?
- AAccept the residual risk with documented, informed sign-off from the business owner.check_circle Correct
- BTransfer the exposure to an insurer so the financial impact falls on a third party.
- CAvoid the risk by retiring the underlying activity that generates the exposure.
- DMitigate further by adding controls until the residual sits below appetite.
Recognise that informed risk acceptance is appropriate when the cost of further treatment exceeds the potential loss and the owner accepts the exposure. Risk acceptance is justified when the marginal cost of additional controls would exceed the value at risk; the practitioner records the decision with informed business-owner sign-off so the residual exposure is owned and accountable rather than ignored.
Why A is correct: When treatment cost exceeds the potential loss and the owner accepts the exposure, formal informed acceptance is the economically rational and accountable choice.
Why B is wrong: Transfer through insurance shifts financial impact but adds premium cost, which is hard to justify when the residual loss is already smaller than further treatment spend.
Why C is wrong: Avoidance removes the activity entirely, an extreme response that sacrifices business value when the exposure is only marginally above appetite.
Why D is wrong: Adding controls feels safe, but spending more than the loss is worth destroys value and is not warranted for a marginal breach of appetite.
What you must be able to do. Given a technology or security scenario, recognise the IT risk and recommend the architecture, operational, continuity, lifecycle, security or privacy practice that addresses it, driven by business requirements such as the recovery objective or the data's purpose.
In one sentenceThe knowledge layer: the architecture, operations, continuity, security and privacy concepts a risk practitioner needs to recognise and address IT risk in real systems.
Recall check: answer these from memory first
- A records system has a fifteen-minute recovery point objective but takes nightly full backups to offsite tape. What change aligns the backup arrangement with the RPO?
- What input should drive the order in which systems are recovered in a disaster recovery plan?
- How should enterprise architecture be used when a business unit wants to buy a platform that duplicates an existing capability?
- A loyalty scheme needs only an email to operate but the team proposes collecting dates of birth, addresses and income. What does data minimisation require?
What it tests. Whether you have the technical grounding to spot IT risk and recommend the right practice. Applying enterprise architecture so technology decisions are reviewed against a target state before approval; managing IT operations risk across change, configuration, asset, problem and incident management, including zero trust; managing project and programme delivery risk; applying business continuity and disaster recovery to sustain and restore critical services; addressing risk across the system development life cycle and emerging technology adoption; applying information security concepts to protect confidentiality, integrity and availability; delivering security awareness training that changes behaviour; and applying data privacy and protection principles across the data lifecycle, including data minimisation.
How to study it. Learn each concept by the business requirement that drives the right answer, because the exam tests application, not definitions. For continuity, let the recovery point objective drive backup frequency (a fifteen-minute RPO needs near-continuous replication, not nightly tapes) and let the business impact analysis drive recovery sequencing by criticality and interdependency, never alphabetical or arbitrary order. For architecture, treat the enterprise architecture review as the control that surfaces duplication and integration risk against the target state before a purchase is approved. For privacy, make data minimisation the reflex: collect only what the stated purpose needs, and reject answers that hoard data for undefined future use. Tie each technical fact back to the risk it creates or reduces rather than learning it in isolation.
Easy to confuse
- Recovery point objective versus recovery time objective. The recovery point objective caps tolerable data loss and so drives backup or replication frequency; the recovery time objective caps tolerable downtime and so drives how fast services must be restored. A tight RPO points to continuous replication, a tight RTO points to faster recovery capacity.
- BIA-driven recovery order versus arbitrary recovery order. Recovery sequencing should follow the business impact analysis, restoring the most critical services and prerequisite dependencies first; alphabetical, by-age or by-cost ordering ignores criticality and can leave dependent services waiting on systems recovered last. The BIA, not convenience, sets the order.
- Data minimisation versus masking or broad consent. Data minimisation means not collecting unneeded personal data in the first place, limiting collection to the stated purpose; masking in the UI or obtaining blanket consent still gathers and retains the surplus data and its exposure. The privacy-correct answer reduces what is held, not just who can see it.
Worked example from the CRISC bank
lock_openFree sampleInformation Technology and Securitymedium
A risk practitioner reviews the backup design for a records system whose recovery point objective is fifteen minutes. The team currently performs a full backup every night and keeps the tapes offsite. The practitioner must recommend the change that brings the backup arrangement into line with the stated recovery point objective. Which recommendation should the practitioner make?
- ARetain the nightly full backup but move the offsite tapes to a closer vault so that the media can be retrieved and restored more quickly after a disruption.
- BKeep the nightly schedule but verify each full backup with an integrity check, since reliable nightly copies are sufficient once their restorability is confirmed.
- CIntroduce continuous or near-continuous replication so that committed transactions are captured within fifteen minutes, matching the stated recovery point objective.check_circle Correct
- DReplace the nightly full backup with a weekly full backup plus daily incrementals to cut the storage cost while preserving the overall recovery capability.
Drive backup frequency from the recovery point objective, using near-continuous replication when tolerable data loss is very small. The recovery point objective caps tolerable data loss, so a fifteen-minute target requires capturing changes at least that often, which nightly, incremental or relocated backups cannot achieve and only continuous or near-continuous replication can satisfy.
Why A is wrong: This is tempting because faster retrieval helps restoration, but shortening retrieval time addresses recovery duration and still leaves up to a day of data exposed, breaching the objective.
Why B is wrong: This is plausible because verification improves backup quality, but a verified nightly copy can still lose nearly a day of data, far exceeding the fifteen-minute objective.
Why C is correct: A fifteen-minute objective means at most fifteen minutes of data may be lost, which only continuous or near-continuous replication can deliver, so this aligns the backup arrangement with the objective.
Why D is wrong: This is attractive because it lowers storage use, but daily incrementals still leave up to a day of unprotected data, so the recovery point objective remains unmet.