IT Cert Ready

ISACA

CRISC

Certified in Risk and Information Systems Control

Start practicing

About this certification

CRISC (Certified in Risk and Information Systems Control) is a ISACA certification. IT Cert Ready offers 1,800 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 4 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Governance · 26%
  • Domain 2 · Risk Assessment · 22%
  • Domain 3 · Risk Response and Reporting · 32%
  • Domain 4 · Technology and Security · 20%

Sample CRISC practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. Sample question 1 · Technology and Security (20%)

    Ridgemont Community Health Network, a mid-sized regional healthcare provider operating across four rural counties, has recently deployed an AI-assisted clinical decision support (CDS) tool integrated directly into its electronic health record (EHR) platform. The vendor's technology roadmap indicates the CDS tool will transition from a rule-based inference engine to a large language model (LLM)-based architecture within the next 18 months. During a routine risk review, the risk manager discovers that the current integration uses a legacy HL7 v2 messaging interface with no input validation controls, and that the planned LLM upgrade has not been assessed for algorithmic bias, data poisoning vulnerabilities, or HIPAA minimum necessary data principles. Clinical staff have already begun relying on the tool's recommendations for medication dosing. The organization's enterprise architecture team was not consulted during procurement. As the risk manager, which action should you prioritize FIRST to address the risk exposure introduced by the planned LLM-based upgrade to the clinical decision support tool?

    • A. Require the vendor to delay the LLM upgrade until the organization completes a full HIPAA Security Rule compliance audit of the existing EHR platform.
    • B. Conduct a structured risk assessment of the emerging LLM technology against the current threat landscape, including data poisoning, algorithmic bias, and PHI exposure vectors, and present findings to the risk owner before the upgrade proceeds.
    • C. Implement input validation controls on the existing HL7 v2 interface immediately and treat the LLM upgrade as a separate project outside the current risk register.
    • D. Escalate the procurement bypass to the compliance committee and recommend disciplinary action against the enterprise architecture team for failing to participate in the vendor selection process.
    View answer & explanation

    Correct answer: B. Conduct a structured risk assessment of the emerging LLM technology against the current threat landscape, including data poisoning, algorithmic bias, and PHI exposure vectors, and present findings to the risk owner before the upgrade proceeds.

    [Domain 4 - Technology and Security, Subtopic 4A - Technology Principles - Area 8 - Emerging Technologies] Core Concept: Task 22 requires the risk practitioner to evaluate emerging technologies and environmental changes for threats, vulnerabilities, and opportunities before those changes are operationalized. Correct Answer (B): The LLM-based upgrade represents a material change in the technology environment with distinct risk characteristics - algorithmic bias, data poisoning, and PHI over-exposure - that differ fundamentally from the current rule-based system. The correct first action is to conduct a structured risk assessment of the emerging technology against the current threat landscape and present findings to the risk owner, enabling informed risk treatment decisions before the upgrade proceeds Why the other options are incorrect: Option A: A HIPAA audit of the existing platform does not address the forward-looking risks of the new LLM architecture. Option C: Is partially valid (fixing the HL7 gap is warranted) but treating the LLM upgrade as a separate, out-of-scope item ignores the risk manager's obligation to evaluate emerging technology changes proactively. Option D: Conflates a governance process failure with a risk management response; escalating a procurement issue does not address the substantive technology risk and is not the highest-priority action.

  2. Sample question 2 · Technology and Security (20%)

    A state-level public health department in the southeastern United States recently adopted a DevOps delivery model to accelerate updates to its disease surveillance platform. The platform ingests real-time data from hospitals, clinics, and laboratories across the state. During a post-incident review following an unplanned outage, the risk manager discovers that a developer pushed a configuration change directly to the production environment without completing the standard change advisory board (CAB) review process. The change introduced a misconfiguration that caused a four-hour data ingestion failure during an active disease outbreak monitoring period. The DevOps team argues that the CAB process is too slow for their continuous delivery cadence and that the existing pipeline lacks automated pre-deployment configuration validation controls. As the risk manager evaluating this operational failure within the context of the agency's evolving technology environment, which recommendation MOST effectively addresses both the immediate control gap and the systemic risk introduced by the DevOps adoption?

    • A. Require the DevOps team to revert to the traditional waterfall SDLC model for all production changes to the surveillance platform, eliminating the risk of unauthorized configuration changes.
    • B. Mandate that all future changes, regardless of size, undergo full CAB review before deployment, and impose disciplinary action on the developer who bypassed the process.
    • C. Recommend integrating automated configuration validation and policy-as-code gates into the CI/CD pipeline as preventive controls, while updating the change management framework to define an expedited risk-tiered approval path that accommodates DevOps velocity without eliminating oversight.
    • D. Accept the residual risk of occasional unauthorized changes as an inherent characteristic of DevOps environments and focus risk treatment resources on improving disaster recovery capabilities to reduce outage duration.
    View answer & explanation

    Correct answer: C. Recommend integrating automated configuration validation and policy-as-code gates into the CI/CD pipeline as preventive controls, while updating the change management framework to define an expedited risk-tiered approval path that accommodates DevOps velocity without eliminating oversight.

    [Domain 4 - Technology and Security, Subtopic 4A - Technology Principles - Area 3 - Operations Management (e.g., change management, assets, DevOps, problems, incidents)] Core Concept: Evaluating changes to the technology environment - specifically the adoption of DevOps and CI/CD practices - requires the risk practitioner to identify the control gaps introduced by new operating models and recommend risk treatment that is compatible with the organization's operational objectives rather than simply reimposing legacy controls. Correct Answer (C): Recommend integrating automated configuration validation and policy-as-code gates into the CI/CD pipeline as preventive controls, while updating the change management framework to define an expedited risk-tiered approval path that accommodates DevOps velocity without eliminating oversight. Why the other options are incorrect: Option A: Reverting to waterfall SDLC eliminates the operational benefits of DevOps adoption and does not address the underlying control gap - it is a disproportionate response that ignores the agency's technology roadmap. Option B: Mandating full CAB review for all changes without addressing pipeline automation perpetuates the velocity conflict that caused the bypass, and disciplinary action alone does not remediate the systemic control deficiency. Option D: Accepting unauthorized production changes as inherent to DevOps conflates a correctable control gap with an unavoidable risk, and focusing solely on recovery rather than prevention is inconsistent with sound risk treatment prioritization.

  3. Sample question 3 · Technology and Security (20%)

    Solara Diagnostics, a European mid-market medical device manufacturer, has acquired BioTrack Systems, a smaller U.S.-based startup that developed an AI-driven predictive maintenance platform for manufacturing equipment. BioTrack's platform was built using a continuous deployment model with no formal change management controls, and its AI models are retrained automatically using production data streams. Post-acquisition, Solara's risk manager is tasked with integrating BioTrack's technology into Solara's validated manufacturing environment, which is subject to EU MDR and FDA 21 CFR Part 11 compliance requirements. The CTO wants to preserve BioTrack's agile DevOps culture to maintain innovation velocity, while the Chief Compliance Officer insists that all software changes must go through Solara's formal validation and change control process. The risk manager must recommend a governance approach that addresses the technology risk while enabling accountability across both organizations. Which recommendation should the risk manager make to best balance technology risk governance, regulatory compliance, and stakeholder accountability during the integration of BioTrack's AI platform?

    • A. Suspend all AI model retraining activities indefinitely until BioTrack's platform has been fully re-architected to comply with Solara's existing validation framework, accepting the innovation delay as a necessary risk mitigation.
    • B. Establish a tiered change governance model that applies Solara's formal validation and change control requirements to AI model updates affecting regulated manufacturing processes, while permitting a structured DevOps workflow for non-regulated components, with a defined RACI and escalation path for boundary decisions.
    • C. Allow BioTrack to continue its existing continuous deployment model unchanged for 12 months while Solara develops a new unified policy, provided that BioTrack's team documents all changes retrospectively.
    • D. Transfer full accountability for BioTrack's platform risk to the CTO, since the platform originated outside Solara's environment and the risk manager lacks authority over acquired entities during the integration period.
    View answer & explanation

    Correct answer: B. Establish a tiered change governance model that applies Solara's formal validation and change control requirements to AI model updates affecting regulated manufacturing processes, while permitting a structured DevOps workflow for non-regulated components, with a defined RACI and escalation path for boundary decisions.

    [Domain 4 - Technology and Security, Subtopic 4A - Technology Principles - Area 3 - Operations Management (e.g., change management, assets, DevOps, problems, incidents)] Core Concept: Evaluating emerging technologies - such as AI-driven platforms with automated model retraining - within an M&A integration context requires the risk manager to assess how the acquired technology's operational model interacts with the acquiring organization's regulatory obligations and risk governance structures. Correct Answer (B): Establish a tiered change governance model that applies Solara's formal validation and change control requirements to AI model updates affecting regulated manufacturing processes, while permitting a structured DevOps workflow for non-regulated components, with a defined RACI and escalation path for boundary decisions. A tiered change governance model is the leading practice response because it directly addresses the threat (uncontrolled AI model changes in a regulated environment), preserves innovation opportunity (structured DevOps for non-regulated components), and establishes clear accountability through a RACI matrix and escalation path - satisfying both the CTO's and CCO's legitimate concerns. This approach reflects SDLC and operations management principles applied to an emerging technology context Why the other options are incorrect: Option A: Is overly restrictive and does not balance risk with opportunity, potentially destroying acquisition value. Option C: Permitting uncontrolled continuous deployment in a regulated environment creates immediate compliance exposure under EU MDR and FDA 21 CFR Part 11; retrospective documentation does not constitute validation. Option D: Risk accountability cannot be unilaterally transferred to a functional leader; the risk manager retains the obligation to identify, assess, and communicate technology risks regardless of organizational origin.

  4. Sample question 4 · Technology and Security (20%)

    Vantara Global Bank, a large multinational institution with retail and corporate banking operations spanning 22 countries across Europe, the Middle East, and Africa (EMEA), is in the planning phase of adopting quantum-resistant cryptographic algorithms across its payment messaging infrastructure. The bank's enterprise architecture team has published a technology roadmap indicating that current RSA-2048 encryption used in SWIFT messaging integrations will reach cryptographic obsolescence risk within an estimated seven-to-ten year horizon based on quantum computing advancement projections. The Chief Risk Officer has asked the risk manager to evaluate this emerging technology threat and provide a prioritized risk treatment recommendation. The bank's data lifecycle management policy currently classifies payment instruction data as having a retention requirement of seven years. A parallel internal audit finding has noted that the bank has no documented cryptographic agility plan - meaning there is no defined process for migrating encryption standards without significant system re-engineering. The bank operates under the European Banking Authority (EBA) ICT risk management guidelines, which require institutions to maintain forward-looking technology risk assessments. As the risk manager at Vantara Global Bank, which approach best prioritizes the risk treatment for the quantum computing threat given the identified vulnerabilities and regulatory context?

    • A. Defer all action on quantum-resistant cryptography until the National Institute of Standards and Technology (NIST) post-quantum cryptography standards are formally adopted by the EBA as mandatory requirements, and document the deferral as a risk acceptance in the enterprise risk register.
    • B. Immediately replace all RSA-2048 implementations across the bank's 22-country infrastructure with post-quantum algorithms within the current fiscal year, treating the quantum threat as a critical risk requiring emergency remediation funding.
    • C. Prioritize the development of a cryptographic agility plan as the near-term risk treatment, focusing first on payment data with retention periods that extend into the quantum risk horizon, and incorporate post-quantum migration milestones into the technology roadmap aligned to EBA forward-looking risk assessment requirements.
    • D. Engage the SWIFT network operator to assume full responsibility for quantum-resistant encryption at the network layer, and remove quantum computing risk from Vantara's enterprise risk register on the basis that encryption is a shared infrastructure responsibility.
    View answer & explanation

    Correct answer: C. Prioritize the development of a cryptographic agility plan as the near-term risk treatment, focusing first on payment data with retention periods that extend into the quantum risk horizon, and incorporate post-quantum migration milestones into the technology roadmap aligned to EBA forward-looking risk assessment requirements.

    [Domain 4 - Technology and Security, Subtopic 4A - Technology Principles - Area 5 - Data Lifecycle Management] Core Concept: Evaluating emerging technologies for threats and vulnerabilities requires the risk manager to assess not only the threat timeline but also the organization's current vulnerability posture - in this case, the absence of a cryptographic agility plan - and to prioritize risk treatment in proportion to the actual exposure window. Correct Answer (C): Prioritize the development of a cryptographic agility plan as the near-term risk treatment, focusing first on payment data with retention periods that extend into the quantum risk horizon, and incorporate post-quantum migration milestones into the technology roadmap aligned to EBA forward-looking risk assessment requirements. Why the other options are incorrect: Option A: Deferring action until regulatory mandates are issued ignores the 'harvest now, decrypt later' threat vector and the existing data retention exposure; it also mischaracterizes the situation as acceptable residual risk when a known vulnerability exists. Option B: An emergency full replacement within one fiscal year is operationally infeasible across a 22-country infrastructure and is disproportionate to the seven-to-ten year threat horizon; it conflates urgency with the actual risk timeline. Option D: Transferring quantum encryption responsibility entirely to SWIFT is not feasible - the bank owns the data lifecycle and the encryption decisions at the application layer - and removing the risk from the enterprise risk register would constitute a material omission under EBA ICT risk management requirements.

  5. Sample question 5 · Technology and Security (20%)

    Meridian Fabrications, a mid-sized automotive parts manufacturer in the U.S. Midwest, is integrating a new cloud-based manufacturing execution system (MES) with its decade-old programmable logic controllers (PLCs) on the shop floor. The IT risk manager has been asked to evaluate the technology change before go-live. During the assessment, the risk manager discovers that the cloud MES vendor uses a shared API gateway that is also used by three other manufacturing clients, the PLCs run firmware that has not been patched in four years due to vendor support constraints, and the integration layer transmits real-time production telemetry over an unencrypted channel. The operations team argues that any delay will cost the company $200,000 per week in lost efficiency gains. Leadership is pressing for immediate go-live. As the risk manager at Meridian Fabrications, which action should you recommend FIRST before authorizing the go-live of the cloud MES integration?

    • A. Approve go-live immediately with a post-implementation review scheduled within 90 days, given the financial pressure and the fact that the vendor is a certified cloud provider.
    • B. Require the operations team to document a formal compensating control plan addressing the unencrypted telemetry channel and shared API gateway risk before go-live proceeds, and escalate the unpatched PLC firmware risk to the risk register with an accepted residual risk statement signed by the business owner.
    • C. Halt the integration project indefinitely until all PLC firmware is updated to a supported version and the vendor replaces the shared API gateway with a dedicated instance.
    • D. Transfer the risk entirely to the cloud MES vendor by requiring an updated service-level agreement that holds the vendor liable for any breach resulting from the shared API gateway.
    View answer & explanation

    Correct answer: B. Require the operations team to document a formal compensating control plan addressing the unencrypted telemetry channel and shared API gateway risk before go-live proceeds, and escalate the unpatched PLC firmware risk to the risk register with an accepted residual risk statement signed by the business owner.

    [Domain 4 - Technology and Security, Subtopic 4A - Technology Principles - Area 8 - Emerging Technologies] Core Concept: When evaluating emerging technology integrations involving cloud platforms and legacy OT systems, the risk manager's role is to identify threats and vulnerabilities, assess their materiality, and recommend proportionate risk treatment - not to unilaterally block or blindly approve projects. Correct Answer (B): Require the operations team to document a formal compensating control plan addressing the unencrypted telemetry channel and shared API gateway risk before go-live proceeds, and escalate the unpatched PLC firmware risk to the risk register with an accepted residual risk statement signed by the business owner. Why the other options are incorrect: Option A: Approving go-live without any control remediation ignores material vulnerabilities and abdicates the risk manager's responsibility to surface and treat risk. Option C: An indefinite halt is disproportionate; it ignores compensating controls and does not account for the business's risk appetite or the feasibility of patching legacy OT firmware. Option D: Contractual risk transfer does not eliminate operational or reputational impact from a breach; it is a partial treatment, not a complete risk response, and the shared API gateway risk remains active regardless of SLA language.

CRISC exam prep FAQ

What is the passing score for the CRISC exam?
The CRISC exam uses a scaled score. A common published passing threshold is 450 out of 800 points. Always confirm the current requirement on the official ISACA exam guide before you sit for the test.
How many questions are on the CRISC certification exam?
The live CRISC exam typically includes 150 questions with about 4 hours on the clock. Formats can vary by delivery mode and exam update.
How do domain quizzes help with CRISC exam prep?
Domain quizzes on IT Cert Ready let you practice CRISC one blueprint domain at a time across 4 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many CRISC practice questions are on IT Cert Ready?
IT Cert Ready includes 1,800 published CRISC practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.