Isaca Updated CRISC Exam Questions and Answers by dolcie

Penetration testing is the best method for assessing control effectiveness against technical vulnerabilities that could be exploited to compromise an information system, as it simulates areal-world attack scenario and evaluates the security posture of the system. Penetration testing is a type of security testing that involves performing authorized and ethical hacking activities on a system to identify and exploit its vulnerabilities and weaknesses. Penetration testing can help to measure and improve the effectiveness and efficiency of the controls implemented to protect the system from unauthorized access, modification, or damage.

The other options are not the best methods for assessing control effectiveness against technical vulnerabilities that could be exploited to compromise an information system. Vulnerability scanning is an automated process that uncovers potential vulnerabilities in systems and software, but it does not provide information on the impact and severity of the vulnerability or how they can be exploited using different exploitation techniques1. Systems log correlation analysis is a process of examining and analyzing the records of system activities and events, but it does not directly test the controls or simulate the attack scenarios. Monitoring of intrusion detection system (IDS) alerts is a process of tracking and auditing the system or network for any signs of malicious or anomalous activities, but it does not evaluate the control performance or identify the root causes of the vulnerabilities. References = Vulnerability Assessment Principles | Tenable®, A Complete Guide on Vulnerability Assessment Methodology, Karen Scarfone Scarfone Cybersecurity - NIST Computer Security Resource …

The risk register is a document that records the identified risks, their analysis, and their responses. It is a useful tool for monitoring and controlling the risks throughout the project lifecycle. However, the risk register is not a static document and it should be updated regularly to reflect the changes in the risk environment and the project status. Therefore, when reviewing therisk register, a risk practitioner should not only look at the risk ratings, but also the assumptions and the rationale behind them. Different business units may have different perspectives, contexts, and data sources for the same risk scenario, which can result in significant variances in inherent risk. Inherent risk is the risk level before considering the existing controls or responses. Therefore, the best course of action is to review the assumptions of both risk scenarios to determine whether the variance is reasonable or not. This can help to identify any errors, inconsistencies, or biases in the risk assessment process, and to ensure that the risk register reflects the current and accurate state of the risks. References = Risk and Information Systems Control Study Manual, Chapter 3, Section 3.2.1, p. 106-107

 A violation of segregation of duties is when the same person performs two or more conflicting tasks that could compromise the security or integrity of a system or process. In the context of IT risk management, segregation of duties aims to prevent fraud, errors, sabotage, theft, misuse of information, and other security breaches. One of the common categories of functions to be separated is the authorization function, which involves evaluating and approving transactions or changes. Another category is the custody function, which involves managing or accessing physical or digital assets. A programmer who writes and promotes code into production is performing both the authorization and the custody functions, which creates a high-risk conflict.The programmer could introduce malicious or erroneous code into the system without proper review or approval, and potentially cause harm to the organization or its stakeholders. Therefore, this scenario is a violation of segregation of duties. References =

Segregation of Duties: Examples of Roles, Duties & Violations

Separation of duties - Wikipedia

Segregation of duties: prevent fraud and error - eftsure

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