Isaca Updated CRISC Exam Questions and Answers by mylo

User recertification is the most effective control to ensure user access is maintained on a least-privilege basis, as it involves a periodic review and validation of user access rights and privileges by the appropriate authority. User recertification helps to identify and remove any unnecessary, excessive, or obsolete access rights and privileges that may pose a security risk or violate the principle of least privilege. User recertification also helps to ensure that user access rights and privileges are aligned with the current business needs, roles, and responsibilities of the users.

The other options are not the most effective controls to ensure user access is maintained on a least-privilege basis. User authorization is the process of granting or denying access rights and privileges to users based on their identity, role, and credentials, but it does not verify or update the existing access rights and privileges of the users. Change log review is the process of examining and analyzing the records of changes made to the system, configuration, or data, but it does not directly address the user access rights and privileges. Access log monitoring is the process of tracking and auditing the user activities and actions on the system or network, but it does not validate or modify the user access rights and privileges. References = What Is the Principle of Least Privilege and Why is it Important?, Principle of Least Privilege: Definition, Methods & Examples, IT Risk Resources | ISACA

The best way to facilitate the alignment of IT risk management with enterprise risk management (ERM) is to link IT risk scenarios to enterprise strategy, because this ensures that the IT risks are considered in the context of the enterprise’s mission, vision, and goals. Linking IT risk scenarios to enterprise strategy also helps to prioritize the IT risks based on their impact and relevance to the enterprise’s objectives, and to select the appropriate risk responses and resources. The other options are not the best ways to facilitate the alignment of IT risk management with ERM, because they do not address the integration or alignment of the IT and enterprise perspectives. Adopting qualitative or quantitative enterprise risk assessment methods, and linking IT risk scenarios to technology objectives are examples of techniques or tools that can be used to perform IT risk management or ERM, but they do not ensure the alignment or consistency of the two processes. References = Risk and Information Systems Control Study Manual, 7th Edition, Chapter 1, Section 1.2.3, p. 22.

The likelihood rating in the risk register is a measure of how probable it is that a risk event will occur, given the current conditions and controls. The risk practitioner should change the likelihood rating if there is a significant change in the effectiveness of the controls that are implemented to prevent or reduce the risk. For example, if a control becomes obsolete, ineffective, or bypassed, the likelihood rating should increase, as the risk event becomes more likely to happen. Conversely, if a control becomes more efficient, reliable, or robust, the likelihood rating should decrease, as the risk event becomes less likely to happen. The other options are not likely to cause a change in the likelihood rating, as they are not directly related to the probability of the risk event. Risk appetite is the amount of risk that an organization is willing to accept in pursuit of its objectives. Control cost is the amount of resources that are required to implement and maintain a control. Risk tolerance is the acceptable level of variation that an organization is willing to allow for a risk to deviate from its desired level or expected outcome. These factors may influence the risk response or the risk acceptance, but not the likelihood rating. References = Risk and Information Systems Control Study Manual, Chapter 1: IT Risk Identification, Section 1.4: Risk Register, p. 25-26.

A change management process is a set of procedures and activities that aim to ensure that changes in an organization’s IT systems and services are implemented in a controlled and coordinated manner. The effectiveness of a change management process can be measured by how well it reduces the risks and costs associated with changes, and how well it supports the business objectives and customer expectations. One of the best metrics to demonstrate the effectiveness of a change management process is the percent of unauthorized changes. Unauthorized changes are changes that are made without following the established change management process, such as obtaining approval, documenting the change, testing the change, and communicating the change. Unauthorized changes can introduce errors, defects, security breaches, and disruptions to the IT systems and services, and can negatively affect the business performance and customer satisfaction. Therefore, a low percent of unauthorized changes indicates that the change management process is effective in ensuring that changes are properly planned, approved, executed, and monitored. The other options are not the best metrics to demonstrate the effectiveness of a change management process, as they do not directly reflect the quality and control of the changes. An increase in the frequency of changes may indicate that the organization is agile and responsive to the changing business needs and customer demands, but it does not necessarily mean that the changes are well-managed and beneficial. An increase in the number of emergency changes may indicate that the organization is able to handle urgent and critical situations, but it may also suggest that the organization is reactive and lacks proper planning and analysis of the changes. The average time to complete changes may indicate the efficiency and speed of the change management process, but it does not measure the effectiveness and value of the changes. References = CRISC Review Manual, pages 156-1571; CRISC Review Questions, Answers & Explanations Manual, page 712