The primary focus of an IT risk awareness program is to cultivate long-term behavioral change. An IT risk awareness program is a program that educates and informs the stakeholders, such as the employees, managers, customers, or partners, about the IT risks and the IT risk management activities. An IT risk awareness program helps to increase the knowledge and understanding of the IT risks and the IT risk management objectives, strategies, and processes, and to promote the participation and collaboration of the stakeholders in the IT risk management activities. The primary focus of an IT risk awareness program is to cultivate long-term behavioral change, which is the change in the attitudes, beliefs, values, and actions of the stakeholders regarding the IT risks and the IT risk management activities. Cultivating long-term behavioral change helps to create and sustain a risk-aware culture, which is a culture that recognizes, respects, and supports the IT risk management activities, and that encourages the stakeholders to take responsibility and ownership of the IT risks and the IT risk management activities. Cultivating long-term behavioral change also helps to improve the effectiveness and efficiency of the IT risk management activities, and to align the IT risk management activities with the business goals and values. Ensuring compliance with the organization's internal policies, communicating IT risk policy to the participants, and demonstrating regulatory compliance are not the primary focus of an IT risk awareness program, as they are either the benefits or the objectives of the IT risk awareness program, and they do not address the primary need of changing the behavior of the stakeholders. References = CRISC Review Manual, 6th Edition, ISACA, 2015, page 36.

The first step for the risk practitioner to address the situation of extended network outages that have exceeded tolerance is to recommend a root cause analysis of the incidents. A root cause analysis is a process of identifying and resolving the underlying causes of a problem or an event. By performing a root cause analysis, the risk practitioner can determine why the network outages occurred, what factors contributed to them, and how they can be prevented or reduced in the future. Recommending additional controls, updating the risk tolerance level, and updating the incident-related risk trend are possible steps that may follow the root cause analysis, but they are not the first step. References = ISACA Certified in Risk and Information Systems Control (CRISC) Certification Exam Question and Answers, question 4; CRISC Review Manual, 6th Edition, page 153.

A control owner's primary responsibility is to ensure that the controls under their purview are effectively implemented and functioning as intended to mitigate associated risks. This involves regular monitoring, evaluation, and reporting on the performance of controls to maintain the organization's risk posture within acceptable limits.
Reference:ISACA CRISC Review Manual, 7th Edition, Chapter 3: Risk Response and Reporting, Section:
Risk Response.

The first thing that should be done by IT governance to support the development of a new risk management plan to specifically address legal and regulatory risk scenarios is to establish IT-specific compliance objectives. Compliance objectives are the goals or targets that the organization sets to ensure that its IT activities and processes comply with the relevant laws, regulations, standards, and contracts. Compliance objectives help to define the scope, criteria, and expectations for the IT compliance program, and to align the IT compliance activities with the organization's strategy, risk appetite, and performance measures.
Compliance objectives also help to communicate and demonstrate the organization's commitment and accountability for IT compliance to the internal and external stakeholders, such as the board, management, regulators, auditors, and customers. The other options are not the first thing that should be done, although they may be useful or necessary steps or components of the IT compliance program. Requesting a regulatory risk reporting methodology, requiring critical success factors (CSFs) for IT risks, and communicating IT key risk indicators (KRIs) and triggers are all activities that can help to implement and monitor the IT compliance program, but they require the prior definition and agreement of the IT compliance objectives. References = Risk and Information Systems Control Study Manual, Chapter 2, Section 2.4.1, page 2-37.

User accounts provisioning is the process of creating, managing, and modifying user accounts within a system or an application, based on the user's roles, responsibilities, and requirements. User accounts provisioning is an essential part of identity and access management (IAM), which aims to ensure the confidentiality, integrity, and availability of the system or the application, and the information or resources that it handles or supports1.
The best key performance indicator (KPI) for monitoring adherence to an organization's user accounts provisioning practices is the percentage of accounts without documented approval, because it can help to measure how well the organization follows the policies, standards, and procedures for user accounts provisioning, and how effectively the organization controls andaudits the user accounts provisioning activities. The percentage of accounts without documented approval can indicate:
The level of compliance and accountability of the user accounts provisioning process, and the extent to which the user accounts provisioning requests and actions are authorized and verified by the appropriate parties, such as managers, IT staff, or security officers The level of risk and exposure of the user accounts provisioning process, and the likelihood and impact of unauthorized or inappropriate user accounts provisioning, such as granting excessive or unnecessary access privileges, creating duplicate or fraudulent accounts, or violating legal or regulatory requirements The level of quality and efficiency of the user accounts provisioning process, and the ability and capacity of the organization to manage and maintain the user accounts provisioning records and documents, such as forms, logs, or reports23 The other options are not the best KPIs for monitoring adherence to an organization's user accounts provisioning practices, but rather some of the factors or outcomes of it. User accountswith default passwords are user accounts that have not changed their passwords from the initial or default values that are assigned by the system or the application. User accounts with default passwords are a factor that can increase the risk of unauthorized or malicious access to the system or the application, as the default passwords may be easily guessed or compromised by attackers. Active accounts belonging to former personnel are user accounts that have not been deactivated or deleted after the users have left the organization. Active accounts belonging to former personnel are an outcome of ineffective or inefficient user accounts deprovisioning, which is the process of revoking or removing the user accounts and access privileges when they are no longer needed or valid. Accounts with dormant activity are user accounts that have not been used or accessed for a long period of time. Accounts with dormant activity are an outcome of poor or inconsistent user accounts management, which is the process of updating or modifying the user accounts and access privileges according to the changes or needs of the users or the organization4. References = User Provisioning for SaaS Apps: Top 10 Best Practices | Resmo Top Identity and Access Management Metrics KPI-driven approach to Identity & Access Management - Elimity
[CRISC Review Manual, 7th Edition]