Study guide
AI, Blockchain, and Ransomware Context
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
AI, Blockchain, and Ransomware Context
Key Takeaways Explain This Topic AI
Emerging technology is governed the same way as any asset: risk-assess against business objectives before adoption, not after.
Generative AI introduces data-leakage, model-poisoning, prompt-injection, and shadow-AI risks that an acceptable-use policy must address.
Blockchain offers integrity and non-repudiation but cannot fix bad input data and complicates the right to erasure.
Ransomware defense favors prevention plus tested, offline, immutable backups; paying the ransom is a last-resort business decision, not a control.
Last updated: November 2026
AI, Blockchain, and Ransomware Context
Emerging technology tempts candidates into technical rabbit holes. CISM keeps it managerial: every new technology is governed by the same risk process — understand the business objective, identify the new risks, decide treatment against risk appetite, assign ownership, and monitor. The answer to "the business wants to adopt X" is almost never "ban it" or "adopt it immediately"; it is assess and govern.
Generative AI and large language models
The fastest-growing exam topic. The distinct risks a security manager must address:
AI risk Description Control direction
Data leakage Staff paste confidential data into public models Acceptable-use policy, approved enterprise tools, DLP
- Shadow AI Unapproved AI tools used by business units Discovery, sanctioned alternatives, governance
- Prompt injection Malicious input manipulates model output Input validation, output review, least privilege
- Model poisoning Tainted training data corrupts results Trusted data sources, integrity controls
- Hallucination / bias Confident but wrong or unfair output Human-in-the-loop, accountability for decisions
The foundational control is an AI acceptable-use policy plus approved tooling — governance first, technical filters second.
Blockchain and distributed ledgers
CISM tests one nuance: blockchain provides strong integrity and non-repudiation (tamper-evident, immutable records) but it cannot guarantee the truth of the data entered — "garbage in, garbage permanently in." Immutability also collides with privacy rights such as the right to erasure (GDPR), because you cannot easily delete a record from a ledger. Smart-contract code flaws are a real risk and must be reviewed like any application.
Ransomware
Ransomware is the highest-impact threat in this chapter. The defensible posture is resilience, not payment :
Prevention: patching, email filtering, least privilege, network segmentation, and user awareness.
Detection and response: tested incident-response plan with defined roles.
Recovery: tested, offline or immutable backups following the 3-2-1 rule (3 copies, 2 media types, 1 off-site). The trap is assuming online backups suffice — modern ransomware deliberately encrypts reachable backups.
Payment: a last-resort business decision weighing legal, ethical, and sanctions risk (paying may be illegal and does not guarantee recovery). It is never a security control .
Worked scenario
A product team wants to feed customer-support transcripts into a public AI chatbot to draft replies. The strongest CISM action is to classify the data, define an acceptable-use policy that prohibits confidential data in unsanctioned models, offer an approved enterprise tool with data controls, and assign ownership — not to ban AI outright or to allow it because "everyone is using it."
Common traps
Banning emerging tech instead of governing it (or adopting it with no assessment).
Believing blockchain validates the accuracy of data, not just its integrity.
Relying on online backups against ransomware, or treating ransom payment as a control.
Ignoring shadow AI as a data-governance and policy gap.
Governing AI as a third-party and data problem
Much of AI risk is really the chapter's earlier themes in new clothing. A public large-language-model service is a third party that processes your data, so the contract, monitoring, and data-classification disciplines all apply: what does the provider do with prompts, is data used to train shared models, where is it processed, and can the enterprise opt out? When AI is embedded in a vendor's product, it becomes a fourth-party consideration. The CISM extends existing governance rather than inventing a parallel one — an AI acceptable-use policy sits on top of the data-classification and third-party programs already in place.
Ransomware as an incident-management bridge
Ransomware connects this chapter to the Incident Management domain, which carries 29% of the exam. A defensible response is not improvised: it follows a tested incident-response plan with defined roles, an isolation step to limit spread, decision criteria for engaging law enforcement and legal counsel, communication plans for regulators and customers, and recovery from verified clean backups.
The most-tested judgment is sequence and authority — containment and evidence preservation come before restoration, and the decision on whether to pay is escalated to executive and legal leadership, weighed against sanctions exposure, because paying may be unlawful and never guarantees a working key.
Emerging tech and risk appetite
Across AI, blockchain, and beyond, the governing question is always whether the residual risk after controls fits the enterprise's stated risk appetite . New technology often promises business value that justifies accepting some new risk; the CISM's job is to make that trade-off explicit, documented, owned, and monitored, so adoption is a deliberate management decision rather than an unexamined default. That is the difference between governing innovation and being governed by it.
A quick contrast captures the right instinct across all three technologies. For AI, the reflex answer "ban it" loses to "assess, set policy, provide an approved tool." For blockchain, "it makes data trustworthy" loses to "it makes data tamper-evident, but not necessarily true." For ransomware, "keep good online backups" loses to "keep tested, offline or immutable backups and never treat payment as a control." In each case the winning answer is governance-led, proportional, and owned.
Emerging technology questions look intimidating because the terms are new, yet they yield to the same management discipline the rest of the program uses — which is precisely why the CISM blueprint can fold them into existing domains rather than testing them as standalone engineering trivia.