ISACA CISM guideStudy & preparation

CISM Risk Management: Assess, Prioritize and Choose a Response

Published 6 min read3 official sources

Short answer

Information Security Risk Management accounts for 20% of the updated CISM exam, according to ISACA. To practice management decisions, connect a threat and vulnerability to business impact and likelihood, compare response options, identify the authority to decide, and specify follow-up evidence. The NIST-based worksheet here is an original learning exercise, not an official CISM question or a required exam-answer sequence.

What belongs in a CISM management risk decision?

Information Security Risk Management accounts for 20% of the updated CISM exam, according to ISACA's announcement checked November 3, 2026. For this domain, practice explaining the business consequence, the evidence behind your assessment, the response options and the authority needed to choose among them.

The updated outline took effect November 3, 2026. The examples below use NIST's Cybersecurity Framework 2.0, checked November 5, 2026, as supplementary learning material. NIST connects response choices to organizational mission, stakeholder expectations, appetite and tolerance, impact and likelihood. It also calls for responses to be prioritized, planned, tracked and communicated.

Use this original exercise: a fictional manufacturer relies on a supplier's service to maintain its production schedule. Management wants accurate schedules and continued production. The security team has identified two concerns: overly broad supplier access and uncertain recovery from a service outage.

Start a decision record with these questions:

  1. Which business activity and outcome are at stake?
  2. What could happen, through which weakness, and with what consequence?
  3. What evidence supports likelihood and impact, and what remains unknown?
  4. Which response fits the organization's direction and available resources?
  5. Who can authorize it, and what will show whether it is working?

This is a study worksheet, not a mandatory NIST form or an ISACA answer sequence. Complete the business-purpose line before comparing controls.

How do threats, vulnerabilities, likelihood and impact differ?

NIST SP 800-12 Revision 1, checked November 3, 2026, provides the foundational distinction between threats, vulnerabilities, likelihood and impact. For study purposes, separate what could cause harm from the weakness that makes harm possible, then assess how plausible the event is and what it would mean for the business.

The following facts are invented for this exercise. They are not evidence about a real supplier or a recalled exam item.

Decision fieldUnauthorized schedule changesSupplier-service interruption
Potential eventA supplier user changes production instructions without authorization.The scheduling service becomes unavailable.
Weakness or uncertaintySupplier accounts can change schedules outside their assigned work.The manufacturer has no evidence that the supplier can restore the service within the business's needed period.
Available evidenceAn access review confirms the excessive permissions.A manual fallback was successfully tested for one production shift.
Business impact to examineIncorrect instructions could disrupt production.Staff could use the tested fallback initially; consequences beyond that shift remain uncertain.
Missing informationHow the accounts are used and what detects improper changes.Supplier recovery evidence and whether the fallback can sustain longer interruptions.

Do not turn “we have no recovery evidence” into “an outage is certain.” Equally, a successful fallback test for one shift does not establish that every interruption is manageable. Write the gap as a gap and identify what information would resolve it.

For either row, express the risk in a sentence connecting the event, weakness and business consequence. If you are comparing additional study resources, check future availability of full CISM prep, planned for launch, before choosing your next resource.

Why do business context and authority change priority?

NIST's framework uses impact and likelihood to inform prioritization alongside organizational context. A technical severity label alone therefore does not complete this exercise. The manufacturer needs to understand what each finding means for production, which safeguards already exist and how reliable the supporting evidence is.

Suppose the scenario adds that improper schedule changes would reach production without review, while the tested fallback remains available for an interruption. Restricting unnecessary change permissions has a concrete connection to the first exposure. Obtaining recovery evidence remains an assigned action because the fallback's longer-term limits are unresolved.

That is a reasoned provisional choice, not proof that access findings always outrank availability risks. If the fallback becomes unusable or the supplier reports an imminent interruption, revisit the comparison. State which changed fact affects your recommendation.

Authority is a separate check. NIST calls for defined responsibilities, authorities and leadership accountability. In this fictional organization, assume the operations director has delegated authority to approve the relevant production risk, the security manager recommends a response, and an IT service owner implements access changes. Those titles belong to the example; they are not universal CISM risk-owner assignments.

Before recording a decision, identify the applicable organizational direction and who is authorized to approve it. Once approved, the CISM security-program development guide shows how to turn that direction into assigned work, resources and evidence of progress.

When do avoidance, mitigation, transfer or acceptance fit?

NIST identifies mitigation, transfer, avoidance and acceptance as possible responses to negative risks. Compare them against the specific exposure and business objective. The following applications are editorial examples, not official exam answers.

ResponseApplication to the fictional serviceWhat the decision still needs
AvoidStop an optional supplier integration that creates an exposure the business will not take.A decision about the business capability being given up.
MitigateNarrow supplier permissions and verify that the revised access supports authorized work.An action owner and evidence that the intended restriction works.
TransferConsider an arrangement allocating a defined part of the exposure to another party.Clarity about the scope transferred, what remains and who monitors the relationship.
AcceptAn authorized decision-maker agrees to retain a stated exposure under the organization's direction.A documented rationale, remaining exposure and a review point.

Transfer should not be treated as removing the organization's need for oversight. NIST also calls for supplier risks to be monitored throughout relationships. Identify what the arrangement actually covers instead of writing “the vendor owns everything.”

Acceptance also needs an actual decision. In this exercise, an unanswered assessment request is still an open item; it is not evidence that an authorized person approved the exposure. If a recommendation exceeds the decision-maker's authority, identify the required approval route.

Write a short justification for your preferred response and explain what fact could make another option more suitable. When comparing preparation choices for this topic, review the future availability of full CISM prep, planned for launch.

What should be tracked after a response is chosen?

A decision record needs follow-through. NIST includes tracking and communicating responses, reviewing performance, and handling changes and exceptions. For the manufacturer's worksheet, use the following original follow-up fields:

  • Decision and rationale: what was approved and why it fits the business need.
  • Authority and action owner: who approved the exposure and who will perform the work.
  • Implementation evidence: for example, a reviewed access list and a check of the revised permissions.
  • Remaining uncertainty: recovery evidence still requested from the supplier and limitations of the tested fallback.
  • Review point or trigger: a planned review, a material service change, a failed control check or new supplier information.

Do not close the unauthorized-change concern merely because a request to adjust permissions was submitted. In this example, closure needs the agreed evidence of implementation and a decision about what exposure remains. Review the outage concern when the supplier provides recovery evidence, then revise the assessment if that evidence changes the assumptions.

If an incident occurs, the CISM incident-management leadership guide addresses authority, communication and recovery decisions. Keep this worksheet focused on assessing and managing the exposure.

For your next study session, change one fact in the fictional case and rewrite the recommendation. Check whether the response, approval and follow-up still fit. If you want another preparation option later, see if full CISM prep, planned for launch, suits a later risk-management review.

Trust the source

Official sources

Exam policies can change. Use these primary sources for the most current details.