CRISC Exam Dumps - Certified in Risk and Information Systems Control

 The FIRST thing that the organization should do to reduce the risk of data exposure when modifying its system to enable acceptance of credit card payments is to conduct a risk assessment, because it is a process that involves identifying and analyzing the potential risks, threats, and vulnerabilities that may affect the system and the data, and their likelihood and impact on the business objectives and processes. A risk assessment can help to determine the current risk level and exposure, and to provide the basis for selecting and implementing the appropriate risk responses and controls. The other options are not the first thing that the organization should do, because:

Option B: Updating the security strategy is a result of conducting a risk assessment, but not the first thing that the organization should do. A security strategy is a plan that defines the security objectives, policies, standards, and procedures for the system and the data, and it should be aligned with the risk assessment results and the business requirements and expectations.

Option C: Implementing additional controls is a response to the risk assessment results, but not the first thing that the organization should do. Controls are the measures that are designed and implemented to prevent or reduce the occurrence or impact of the risks, threats, and vulnerabilities, and to ensure the confidentiality, integrity, and availability of the system and the data.

Option D: Updating the risk register is a part of the risk assessment process, but not the first thing that the organization should do. A risk register is a tool that documents and tracks the identified risks, their characteristics, their status, and their responses, and it should be updated regularly to reflect the current risk profile and exposure of the system and the data. References = Risk and Information Systems Control Study Manual, 7th Edition, ISACA, 2020, p. 108.

IT risk scenarios are hypothetical situations that describe how IT-related risks can affect the organization’s objectives, operations, or assets1. IT risk scenarios help to make IT risk more concrete and tangible, and to enable proper risk analysis and assessment2. IT risk scenarios are developed after IT risks are identified, and are used as inputs for risk analysis, where the frequency and impact of the scenarios are estimated3.

The most important factor to the successful development of IT risk scenarios is threat and vulnerability analysis. Threat and vulnerability analysis is the process of identifying and evaluating the potential sources and causes of IT risks, such as malicious actors, natural disasters, human errors, or technical failures4. Threat and vulnerability analysis can help to:

Define the scope and boundaries of the IT risk scenarios, and ensure that they are relevant and realistic

Identify the critical assets, processes, or functions that are exposed or affected by the IT risks, and assess their value and importance to the organization

Determine the likelihood and methods of the threat events, and the existing or potential weaknesses or gaps in the IT control environment

Estimate the potential consequences and impacts of the IT risks, such as financial losses, operational disruptions, reputational damages, or compliance violations5

References = IT Scenario Analysis in Enterprise Risk Management - ISACA, IT Risk Scenarios - Morland-Austin, Threat and Vulnerability Analysis - Wikipedia, Threat and Vulnerability Analysis - ISACA

The risk practitioner’s BEST course of action is to validate the transfer of risk and update the register to reflect the change, because outsourcing the backup and recovery procedures to a third-party cloud provider does not eliminate the risk, but rather transfers it to the service provider. The risk practitioner should verify that the service provider has adequate controls and capabilities to handle the backup and recovery procedures, and that the contractual agreement specifies the roles and responsibilities of both parties. The risk practitioner should also update the risk register to reflect the new risk owner and the residual risk level. The other options are not the best course of action, because:

Option A: Accepting the risk and documenting contingency plans for data disruption is not the best course of action, because it implies that the risk practitioner is still responsible for the risk, even though it has been transferred to the service provider. Contingency plans are also reactive measures, rather than proactive ones.

Option B: Removing the associated risk scenario from the risk register due to avoidance is not the best course of action, because it implies that the risk has been eliminated, which is not the case. The risk still exists, but it has been transferred to the service provider. The risk register should reflect the current risk status and ownership.

Option C: Mitigating the risk with compensating controls enforced by the third-party cloud provider is not the best course of action, because it implies that the risk practitioner is still involved in the risk management process, even though the risk has been transferred to the service provider. The risk practitioner should rely on the service provider’s controls and capabilities, andmonitor their performance and compliance. References = Risk and Information Systems Control Study Manual, 7th Edition, ISACA, 2020, p. 196.

The next step for the risk practitioner when a key external technology supplier refuses to provide control design and effectiveness information is to review the supplier’s contractual obligations. The contract between the organization and the supplier should specify the terms and conditions for the provision of the service or function, including the requirements for control design and effectiveness information. By reviewing the contract, the risk practitioner can determine if the supplier is breaching the contract and take appropriate actions to enforce the contract or terminate the relationship. Escalating the non-cooperation to management, excluding applicable controls from the assessment, and requesting risk acceptance from the business process owner are other possible steps, but they are not as effective as reviewing the supplier’s contractual obligations. References = ISACA Certified in Risk and Information Systems Control (CRISC) Certification Exam Question and Answers, question 11; CRISC Review Manual, 6th Edition, page 144.

According to the CRISC Review Manual (Digital Version), the right to audit the provider is the most important factor to help define the IT risk associated with outsourcing activity to a cloud-based service provider, as it enables the organization to verify the compliance and performance of the provider with the contractual obligations and service level agreements. The right to audit the provider helps to:

Assess the security, availability, confidentiality, integrity, and privacy of the data and processes hosted by the provider

Identify and evaluate the risks and controls related to the cloud-based services and the provider’s infrastructure

Monitor and measure the quality and effectiveness of the cloud-based services and the provider’s governance and management practices

Report and resolve any issues or incidents related to the cloud-based services and the provider’s operations

Ensure the alignment of the cloud-based services and the provider’s policies and standards with the organization’s objectives and requirements

References = CRISC Review Manual (Digital Version), Chapter 3: IT Risk Response, Section 3.3: Risk Response Options, pp. 176-1771

Continuous data backup controls are the best recommendation to further reduce the impact of ransomware attacks, as they enable the organization to restore the data that has been encrypted or deleted by the ransomware without paying the ransom or losing the data. Continuous data backup controls ensure that the data is regularly and automatically backed up to a secure and separate location, and that the backup data is tested and verified for integrity and availability. Two-factor authentication, encryption for data at rest, and encryption for data in motion are not the best recommendations to further reduce the impact of ransomware attacks, as they do not address the recovery of the data that has been compromised by the ransomware. These controls may help to prevent or mitigate ransomware attacks, butnot to reduce their impact. References = CRISC by Isaca Actual Free Exam Q&As, question 207; CRISC: Certified in Risk & Information Systems Control Sample Questions, question 207.

A risk treatment plan is a document that outlines the approach and actions to be taken to address the unacceptable risks identified in the risk assessment process1. A risk treatment plan should include the following components2:

The risk identification number and description

The risk treatment option chosen (e.g., avoid, reduce, share, or accept)

The risk treatment owner, who is responsible for implementing and monitoring the risk treatment

The risk treatment actions, which are the specific tasks or steps to be performed to execute the risk treatment

The risk treatment resources, which are the human, financial, or technical resources required to support the risk treatment

The risk treatment target date, which is the deadline for completing the risk treatment

The risk treatment performance indicators, which are the measures to evaluate the effectiveness and efficiency of the risk treatment

The risk treatment status, which is the current progress or outcome of the risk treatment

Among the four options given, the most important component in a risk treatment plan is the treatment plan ownership. This is because the treatment plan ownership defines theaccountability and authority for the risk treatment, and ensures that the risk treatment actions are carried out as planned and reported as required3. The treatment plan ownership also facilitates the communication and coordination among the stakeholders involved in the risk treatment, and enables the escalation and resolution of any issues or challenges that may arise during the risk treatment process4.

References = Risk Treatment (With Examples), ISO 27001 Risk Assessment & Risk Treatment: The Complete Guide, Risk Management Framework - Treat Risks, Risk Management Plan Components