Isaca Updated CRISC Exam Questions and Answers by isla-rose

According to the CRISC Review Manual, the most important reason for implementing change control procedures is to ensure that only approved changes are implemented, because it helps to prevent or minimize the risk of unauthorized or unintended changes that may affect the stability, security, or performance of the IT systems and processes. Change control procedures are the steps and activities that are followed to manage the initiation, review, approval, implementation, and verification of changes. Change control procedures also help to ensure that the changes are aligned with the business requirements and objectives, and that the changes are documented and communicated to the stakeholders. The other options are not the most important reason for implementing change control procedures, as they are related to other benefits or outcomes of the change control process. Timely evaluation of change events is the reason for implementing change management, which is the process of identifying, analyzing, and responding to the changes that may affect the IT systems and processes. An audit trail is the outcome of implementing change control procedures, as it provides a record of the changes and their impacts. Logging emergency changes is the exception of implementing change control procedures, as it allows for bypassing the normal approval process in case of urgent or critical changes. References = CRISC Review Manual, 7th Edition, Chapter 4, Section 4.2.1, page 177.

The maturity of organizational risk management refers to the degree to which risk management is embedded and integrated into the organization’s culture, processes, and decision-making1. A higher level of maturity implies that the organization has a clear and consistent understanding of its risk appetite and tolerance, and that it can effectively identify, assess, respond, monitor, and communicate risks2.

The best way to address the issue of participants focusing on the financial cost to mitigate risk rather than choosing the most appropriate response is to raise the maturity of organizational risk management. This can help to:

Ensure that risk management is aligned with the organization’s strategic objectives and values, and that risk responses are based on the potential impact and likelihood of risks, not just on the cost of mitigation

Foster a risk-aware culture that encourages proactive and collaborative risk management, and that recognizes and rewards good risk management practices

Provide adequate training and guidance for risk management roles and responsibilities, and ensure that risk management skills and competencies are developed and maintained

Implement a robust and consistent risk management framework, methodology, and tools that support the risk management process and enable continuous improvement and learning

Enhance the quality and reliability of risk information and reporting, and ensure that risk management performance and outcomes are measured and evaluated3

References = Risk Maturity Model - Wikipedia, Risk Maturity Model - ISACA, Risk Maturity Model - IRM

 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

A change management process is a set of procedures and activities that ensure that any changes to the IT systems or applications are planned, approved, tested, implemented, and documented in a consistent and controlled manner.

A change management process has recently been updated with new testing procedures. This means that the process has been improved or modified to include new or additional steps or methods for verifying and validating the changes before they are deployed to the production environment.

The next course of action after updating the change management process with new testing procedures is to communicate to those who test and promote changes. This means that the change management team or function should inform and educate the people who are involved or affected by the changes, such as the developers, testers, users, customers, etc., about the new testing procedures, their purpose, benefits, requirements, and expectations.

Communicating to those who test and promote changes helps to ensure that the new testing procedures are understood and followed by all the parties, that the changes are tested and promoted in accordance with the process standards and criteria, and that the changes are delivered with the expected quality and performance.

The other options are not the next courses of action after updating the change management process with new testing procedures. They are either secondary or not essential for change management.

The references for this answer are:

Risk IT Framework, page 27

Information Technology & Security, page 21

Risk Scenarios Starter Pack, page 19