CRISC Exam Results

Project risk register: A document that records the identified risks, their likelihood, impact, and mitigation strategies for a project1.

Project steering committee: A group of senior stakeholders and experts who oversee and support a project from a higher level2.

Risk mitigation actions: The measures taken to prevent, reduce, or transfer the risks that may affect a project3.

The most important objective of regularly presenting the project risk register to the project steering committee is to track the status of risk mitigation actions. Tracking the status of risk mitigation actions can help the project steering committee to:

Monitor and measure the performance and effectiveness of the risk management process and controls

Evaluate the progress and outcomes of the risk mitigation actions against the project goals and objectives

Identify and resolve any issues, challenges, or gaps in the risk mitigation actions

Provide guidance, feedback, and support to the project manager and the project team

Adjust or revise the risk mitigation actions as needed to reflect the changes in the project scope, schedule, budget, or environment

The other options are not the most important objective of regularly presenting the project risk register to the project steering committee, although they may be relevant or beneficial. Allocating budget for resolution of risk issues, which means assigning financial resources to address and resolve the risks that may affect a project, may be a part of the risk management process, but it is not the primary purpose of presenting the project risk register, which is more focused on tracking and reporting the risk status and actions. Determining if new risk scenarios have been identified, which means finding out if there are any additional or emerging risks that may impact a project, may be a useful outcome of presenting the project risk register, but it is not the main objective, which is more concerned with tracking and reporting the existing risk status and actions. Ensuring the project timeline is on target, which means verifying that the project is progressing according to the planned schedule and milestones, may be a benefit of presenting the project risk register, but it is not the key objective, which is more related to tracking and reporting the risk status and actions.

References = Risk Register: A Project Manager’s Guide with Examples [2023] • Asana, Project Steering Committee: Roles, Best Practices, Challenges, Risk Mitigation: Definition, Strategies, and Examples

According to the CRISC Review Manual1, a risk action plan is a document that defines the specific actions, resources, responsibilities, and timelines for implementing the risk responses. A risk action plan should be developed after the results of a vulnerability assessment are shared with the relevant stakeholders, such as the business manager, to address the identified vulnerabilities and mitigate the associated risks. Developing a risk action plan is the next step in the risk management process, as it helps to ensure that the risk responses are executed effectively and efficiently, and that the residual risks are within the acceptable levels. References = CRISC Review Manual1, page 201.

The correct answer isBbecause technical controls affecting access permissions should be implemented according toseparation of duties. Access permissions must be structured so that no single individual has incompatible responsibilities that could enable unauthorized activity, fraud, or unapproved changes. This is a core principle of access control governance and control design.

The other options are less appropriate:

A. Integration testing requirementsrelate to testing system interactions, not the primary basis for assigning access permissions.

C. Configuration baselinesare important for standard settings, but access authorization must first align with role separation and accountability.

D. Contingency scenariosare related to continuity and recovery, not normal access permission design.

Exact Extracts supporting the answer:

“The PRIMARY reason that an enterprise would establish segregation of duties controls is to prevent errors or fraudulent activity on high-risk transactions.”

“The MOST effective control to prevent segregation of duties violations is implementing role-based access.”

“To ensure that developers do not have access to implement changes to production applications an enterprise must have segregation of duties between application development and operations.”

“The control a risk practitioner would recommend is segregation of duties” when personnel can both change system configuration settings and modify logs.

These extracts show that access permissions and technical access controls should be aligned withseparation of dutiesto prevent misuse and reduce risk.

===========

Backups are the best control to mitigate the impact of a failed IT system upgrade project that has resulted in the corruption of an organization’s asset inventory database, as they allow theorganization to restore the data from a previous state and resume normal operations. Encryption, authentication, and configuration are not the best controls, as they do not address the data corruption issue, but rather the datasecurity, access, and quality issues, respectively. References = CRISC Review Manual, 7th Edition, page 153.