You save $69.98
CRISC Premium Bundle
- Premium File 1105 Questions & Answers
- Last Update: Nov 10, 2026
- Training Course 64 Lectures
- Study Guide 498 Pages
You save $69.98
An organization is preventing a recurrence of this risk pattern: A data center replicates files to the recovery site, but ransomware encryption immediately propagates into replicas. Which ongoing safeguard would best prevent recurrence of this specific failure mode?
Test destructive-attack recovery and backup access separation periodically. This safeguard addresses the recurring failure rather than only the current event. The expected verification is: A controlled exercise restores uncompromised records from protected recovery points.
Periodically review retention rules and deletion coverage after system changes. That safeguard prevents failures associated with data retention lifecycle and does not directly prevent this ransomware backup integrity recurrence. The applicable continuing control is: Test destructive-attack recovery and backup access separation periodically.
Enforce risk-based change gates and backout testing. That safeguard prevents failures associated with change management bypass and does not directly prevent this ransomware backup integrity recurrence. The applicable continuing control is: Test destructive-attack recovery and backup access separation periodically.
Require dependency inventory and patch ownership in release governance. That safeguard prevents failures associated with third-party library in sdlc and does not directly prevent this ransomware backup integrity recurrence. The applicable continuing control is: Test destructive-attack recovery and backup access separation periodically.
A risk leader is reviewing this situation: A municipal utility's recovery plans restore control servers but do not define who communicates with emergency responders during outages. Which next step would most directly treat or govern the risk in this situation?
Integrate stakeholder communication roles and emergency dependencies into resilience exercises. Technical recovery and operational coordination both affect business resilience. Evidence that the action has worked would be: Exercise records show timely responder notifications and coordinated service restoration decisions.
Reinforce controlled change authorization, representative testing, and emergency rollback evidence. That change is aimed at change management bypass, whereas this decision must address disaster communications workflow. The relevant first comparison is: Review contact lists, message triggers and exercise notification timings.
Build software composition inventory and vulnerability response into dependency selection and CI/CD. That change is aimed at third-party library in sdlc, whereas this decision must address disaster communications workflow. The relevant first comparison is: Review contact lists, message triggers and exercise notification timings.
Replan the project critical path and document contingency controls for the unresolved identity dependency. That change is aimed at project dependency risk, whereas this decision must address disaster communications workflow. The relevant first comparison is: Review contact lists, message triggers and exercise notification timings.
A risk owner seeks evidence following review of this situation: A municipal utility's recovery plans restore control servers but do not define who communicates with emergency responders during outages. Which evidence would best demonstrate that the intended risk response is functioning?
Exercise records show timely responder notifications and coordinated service restoration decisions. This evidence addresses the stated risk rather than showing only that a control was configured. Technical recovery and operational coordination both affect business resilience.
Change records show approved impact review, test results, implementation and recovery readiness. That observation may help validate change management bypass, but it does not establish the acceptance condition for disaster communications workflow. Here, the decisive evidence is: Exercise records show timely responder notifications and coordinated service restoration decisions.
Portfolio decisions show high-risk authentication work, capacity allocation and measurable delivery checkpoints. That observation may help validate agile portfolio risk prioritization, but it does not establish the acceptance condition for disaster communications workflow. Here, the decisive evidence is: Exercise records show timely responder notifications and coordinated service restoration decisions.
Pilot telemetry and test records show expected federated authentication plus reversible deployment. That observation may help validate production rollout safeguard, but it does not establish the acceptance condition for disaster communications workflow. Here, the decisive evidence is: Exercise records show timely responder notifications and coordinated service restoration decisions.
A governance team is discussing the underlying cause in this situation: A municipal utility's recovery plans restore control servers but do not define who communicates with emergency responders during outages. Which risk-management principle most directly explains the correct approach?
Technical recovery and operational coordination both affect business resilience. This principle links the business exposure to the appropriate response. The immediate management action is: Integrate stakeholder communication roles and emergency dependencies into resilience exercises.
Machine learning risk depends on the trustworthiness of upstream data and operational decision use. That principle is relevant to ai data provenance, not the mechanism implicated by the stated disaster communications workflow situation. In this case: Technical recovery and operational coordination both affect business resilience.
Shared-responsibility boundaries allocate specific technical duties without transferring overall business risk accountability. That principle is relevant to shared responsibility in cloud, not the mechanism implicated by the stated disaster communications workflow situation. In this case: Technical recovery and operational coordination both affect business resilience.
Operational change management controls the risk of unintended service disruption. That principle is relevant to change management bypass, not the mechanism implicated by the stated disaster communications workflow situation. In this case: Technical recovery and operational coordination both affect business resilience.
A risk committee is deciding whether an unresolved exposure can be tolerated: A municipal utility's recovery plans restore control servers but do not define who communicates with emergency responders during outages. What is the most relevant avoidable consequence if the weakness remains unresolved?
Silent restoration activity can delay emergency response and public safety decisions. This consequence follows from the specific missing governance or technical safeguard. Technical recovery and operational coordination both affect business resilience. The appropriate response is: Integrate stakeholder communication roles and emergency dependencies into resilience exercises.
Unchecked production modifications can impair settlement integrity and delay recovery. That potential consequence concerns change management bypass, rather than the direct risk described by disaster communications workflow. Here the material exposure is: Silent restoration activity can delay emergency response and public safety decisions.
Sudden consolidation without transition safeguards can interrupt authentication or create broad common failure. That potential consequence concerns architecture control duplication, rather than the direct risk described by disaster communications workflow. Here the material exposure is: Silent restoration activity can delay emergency response and public safety decisions.
Indefinite retention increases breach impact and potentially conflicts with legal obligations. That potential consequence concerns data retention lifecycle, rather than the direct risk described by disaster communications workflow. Here the material exposure is: Silent restoration activity can delay emergency response and public safety decisions.
Before making a treatment decision, an analyst is investigating this situation: A municipal utility's recovery plans restore control servers but do not define who communicates with emergency responders during outages. Which targeted first investigation would best clarify the risk before action is approved?
Review contact lists, message triggers and exercise notification timings. This isolates the relevant cause before changing unrelated controls. An appropriate follow-up is: Integrate stakeholder communication roles and emergency dependencies into resilience exercises.
Correlate incidents by common router configuration, timing and affected services. That investigation concerns problem versus incident handling and would not isolate the first implicated dependency here. The targeted check is: Review contact lists, message triggers and exercise notification timings.
Review ingestion authentication, outlier patterns and model performance shifts. That investigation concerns ai data provenance and would not isolate the first implicated dependency here. The targeted check is: Review contact lists, message triggers and exercise notification timings.
Compare end-of-support status, reachable interfaces and business impact against roadmap timing. That investigation concerns technology roadmap risk and would not isolate the first implicated dependency here. The targeted check is: Review contact lists, message triggers and exercise notification timings.
An organization is preventing a recurrence of this risk pattern: A municipal utility's recovery plans restore control servers but do not define who communicates with emergency responders during outages. Which ongoing safeguard would best prevent recurrence of this specific failure mode?
Rehearse disaster communications across technical and operational teams. This safeguard addresses the recurring failure rather than only the current event. The expected verification is: Exercise records show timely responder notifications and coordinated service restoration decisions.
Periodically review retention rules and deletion coverage after system changes. That safeguard prevents failures associated with data retention lifecycle and does not directly prevent this disaster communications workflow recurrence. The applicable continuing control is: Rehearse disaster communications across technical and operational teams.
Require dependency maps before material integration and payment changes. That safeguard prevents failures associated with technology exposure dependency and does not directly prevent this disaster communications workflow recurrence. The applicable continuing control is: Rehearse disaster communications across technical and operational teams.
Include cross-vendor dependencies and risk gates in project governance. That safeguard prevents failures associated with project dependency risk and does not directly prevent this disaster communications workflow recurrence. The applicable continuing control is: Rehearse disaster communications across technical and operational teams.
A risk leader is reviewing this situation: An AI assistant is connected to internal contract repositories but can be manipulated into revealing unrelated confidential clauses. Which next step would most directly treat or govern the risk in this situation?
Assess prompt-injection and authorization boundaries and enforce retrieval-scoped access controls. Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools. Evidence that the action has worked would be: Red-team tests confirm untrusted prompts cannot retrieve documents outside the requesting user's rights.
Reinforce controlled change authorization, representative testing, and emergency rollback evidence. That change is aimed at change management bypass, whereas this decision must address generative model leakage. The relevant first comparison is: Trace retrieval identity, access filtering and adversarial prompt paths.
Assess the full authentication, authorization, network and audit chain for the privileged management path. That change is aimed at privileged authentication architecture, whereas this decision must address generative model leakage. The relevant first comparison is: Trace retrieval identity, access filtering and adversarial prompt paths.
Align replacement milestones and interim protections to projected risk and business continuity needs. That change is aimed at technology roadmap risk, whereas this decision must address generative model leakage. The relevant first comparison is: Trace retrieval identity, access filtering and adversarial prompt paths.
A risk owner seeks evidence following review of this situation: An AI assistant is connected to internal contract repositories but can be manipulated into revealing unrelated confidential clauses. Which evidence would best demonstrate that the intended risk response is functioning?
Red-team tests confirm untrusted prompts cannot retrieve documents outside the requesting user's rights. This evidence addresses the stated risk rather than showing only that a control was configured. Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools.
Delivery gates confirm the identity integration is proven before cutover or an approved safe alternative exists. That observation may help validate project dependency risk, but it does not establish the acceptance condition for generative model leakage. Here, the decisive evidence is: Red-team tests confirm untrusted prompts cannot retrieve documents outside the requesting user's rights.
Design artifacts show mapped trust boundaries, requirements and planned security tests before implementation. That observation may help validate secure design stage, but it does not establish the acceptance condition for generative model leakage. Here, the decisive evidence is: Red-team tests confirm untrusted prompts cannot retrieve documents outside the requesting user's rights.
Deletion evidence covers permitted systems, exceptions and third-party confirmation where required. That observation may help validate data-subject request propagation, but it does not establish the acceptance condition for generative model leakage. Here, the decisive evidence is: Red-team tests confirm untrusted prompts cannot retrieve documents outside the requesting user's rights.
A governance team is discussing the underlying cause in this situation: An AI assistant is connected to internal contract repositories but can be manipulated into revealing unrelated confidential clauses. Which risk-management principle most directly explains the correct approach?
Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools. The immediate management action is: Assess prompt-injection and authorization boundaries and enforce retrieval-scoped access controls.
Project dependencies can become enterprise service and data-access risks when sequencing is ignored. That principle is relevant to project dependency risk, not the mechanism implicated by the stated generative model leakage situation. In this case: Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools.
Enterprise architecture choices alter control consistency and concentration risk. That principle is relevant to architecture control duplication, not the mechanism implicated by the stated generative model leakage situation. In this case: Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools.
Key management must follow the data lifecycle and required retention or destruction periods. That principle is relevant to encryption key retirement, not the mechanism implicated by the stated generative model leakage situation. In this case: Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools.
A risk committee is deciding whether an unresolved exposure can be tolerated: An AI assistant is connected to internal contract repositories but can be manipulated into revealing unrelated confidential clauses. What is the most relevant avoidable consequence if the weakness remains unresolved?
Relying on model instructions without technical access boundaries can disclose protected contract data. This consequence follows from the specific missing governance or technical safeguard. Emerging AI interfaces can bridge untrusted text and privileged enterprise data tools. The appropriate response is: Assess prompt-injection and authorization boundaries and enforce retrieval-scoped access controls.
Uncontrolled addressing changes can break critical service reachability and boundary enforcement. That potential consequence concerns hybrid network technical debt, rather than the direct risk described by generative model leakage. Here the material exposure is: Relying on model instructions without technical access boundaries can disclose protected contract data.
Unchecked production modifications can impair settlement integrity and delay recovery. That potential consequence concerns change management bypass, rather than the direct risk described by generative model leakage. Here the material exposure is: Relying on model instructions without technical access boundaries can disclose protected contract data.
Late reviews can force rushed exceptions or launch a weak boundary. That potential consequence concerns secure design stage, rather than the direct risk described by generative model leakage. Here the material exposure is: Relying on model instructions without technical access boundaries can disclose protected contract data.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (1105 Questions, Last Updated on Nov 10, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.