Change management is the best way to prevent an unscheduled application of a patch, because it ensures that any changes to the IT environment are planned, approved, tested, and documented. Change management is a process that controls the implementation of changes to IT systems, applications, infrastructure, or processes. It aims to minimize the risk of disruption, errors, or failures caused by changes. Applying a patch is a type of change that may affect the security, functionality, or performance of an IT system or application. Therefore, applying a patch should follow the change management process and schedule, and avoid any unscheduled or unauthorized patching. Network-based access controls, compensating controls, and segregation of duties are all useful controls to protect the IT environment from unauthorized or malicious access, but they do not prevent an unscheduled application of a patch, as they do not address the change management process.
References = Risk and Information Systems Control Study Manual, Chapter 5, Section 5.4.2, page 211

The business application owner is accountable for business impact and must approve any change that affects application availability. ISACA's CRISC emphasis on ownership roles indicates business owners should approve changes with risk implications.

Biometric systems are preventive controls designed to restrict access to authorized personnel only, thereby proactively mitigating unauthorized access risks. This aligns withAccess and Authentication Controlprinciples in risk management.

According to the CRISC Review Manual1, risk scenarios are hypothetical situations that describe the potential causes, impacts, and responses of a risk event. Risk scenarios are useful tools for identifying, analyzing, and communicating risks in a clear and understandable way. The most important factor when developing risk scenarios is to ensure that they are relevant to the organization, as this helps to capture the specific context, objectives, processes, and resources of the organization, and to reflect the actual risk exposure and appetite of the organization. Relevant risk scenarios also help to engage and involve the stakeholders, and to facilitate risk-based decision making and action planning. References = CRISC Review Manual1, page 206.

The most important outcome of reviewing the risk management process is assuring that the risk profile supports the IT objectives, because this ensures that the organization is managing its IT-related risks in alignment with its business goals and priorities. The risk profile is a summary of the key risks that the organization faces, their likelihood, impact, and response strategies. The IT objectives are the specific and measurable outcomes that the organization expects to achieve from its IT investments and activities.
Byreviewing the risk management process, the organization can evaluate whether the risk profile is accurate, complete, and up-to-date, and whether the risk responses are effective, efficient, and consistent with the IT objectives. The review can also identify any gaps, issues, or opportunities for improvement in the risk management process, and provide recommendations for enhancing the process and its outcomes. The review can also help to communicate and report the value and performance of the risk management process to the senior management, the board of directors, and other stakeholders. References = Risk IT Framework, ISACA,
2022, p. 17