Isaca Updated CRISC Exam Questions and Answers by harri

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

The greatest concern for an IT risk practitioner when an employee transfers to another department is that unnecessary access permissions have not been removed. Unnecessary access permissions are the access rights or privileges that are no longer needed, relevant, or appropriate for the employee’s new role or responsibility. If these access permissions are not removed, they may pose a significant security risk, as the employee may be able to access, modify, or delete sensitive or critical data and systems that are not related to their current function. This may result in data leakage, fraud, sabotage, or compliance violations. The other options are not as concerning as unnecessary access permissions, as they are related to the organizational, operational, or knowledge aspects of the employee transfer, not the security or risk aspects of the employee transfer. References = Risk and Information Systems Control Study Manual, Chapter 3: IT Risk Response, Section 3.3: IT Risk Response Implementation, page 145.

Penetration test resultsprovide direct evidence of the vendor’s technical security posture and ability to defend against real-world attacks. This is more effective than reviewing contracts or benchmarking, which are indirect measures.

Pseudonymizationreplaces identifying fields in a data record with artificial identifiers or pseudonyms. However, unlike full anonymization,re-identification remains possibleif the pseudonym can be matched with external or hidden reference data.

CRISC and privacy-risk guidance (aligned with GDPR principles) emphasize that:

“The primary concern when using pseudonymization as a privacy safeguard is the potential for re-identification of individual data subjects.”

Pseudonymized data can still be linked back to individuals if the mapping key or auxiliary datasets are compromised.

True anonymization eliminates any reasonable means of re-identification, but pseudonymization does not.

Therefore, while pseudonymization reduces exposure, it doesnot fully eliminateprivacy risk.

Options A, B, and D are not inherent to pseudonymization:

Authorized access and update restrictions are policy issues, not intrinsic to pseudonymization.

Other information disclosure (D) could occur through inference but is secondary to direct re-identification.

Hence,C. Individual data subjects can be re-identifiedis the correct and verified answer as per CRISC and GDPR-aligned data protection practices.