PDF CRISC Study Guide

The average time to provision user accounts is the most useful indicator to measure the efficiency of an identity and access management (IAM) process, because it reflects how quickly and smoothly the process can grant access to the appropriate users. The average time to provision user accounts can be calculated by dividing the total time spent on provisioning user accounts by the number of user accounts provisioned in a given period. A lower average time indicates a more efficient IAM process, as it means that users can access the resources they need without unnecessary delays or errors. A higher average time may indicate problems or bottlenecks in the IAM process, such as manual steps, complex workflows, lack of automation, or insufficient resources. The average time to provision user accounts can also be compared across different applications, systems, or business units to identify areas for improvement or best practices. The other options are less useful indicators to measure the efficiency of an IAM process. The number of tickets for provisioning new accounts shows the demand for the IAM process, but not how well the process meets the demand. The password reset volume per month shows the frequency of password-related issues, but not how effectively the IAM process handles them. The average account lockout time shows the impact of account lockouts on user productivity, but not how efficiently the IAM process prevents or resolves them. References = Top Identity and Access Management Metrics 

 According to the CRISC Review Manual (Digital Version), the next course of action when an organization has determined a risk scenario is outside the defined risk tolerance level is to identify risk responses, which are the actions or measures taken to address the risk. Identifying risk responses helps to:

Reduce the likelihood and/or impact of the risk to an acceptable level

Align the risk response with the organization’s risk appetite and risk tolerance

Optimize the value and benefits of the risk response

Balance the costs and efforts of the risk response with the potential losses or damages caused by the risk

Coordinate and communicate the risk response with the relevant stakeholders

References = CRISC Review Manual (Digital Version), Chapter 3: IT Risk Response, Section 3.2: Risk Response Process, pp. 161-1621

 Check totals are IT controls that verify the accuracy and completeness of data by comparing the sum or count of data records or data fields with a predetermined or expected value. Check totals can help detect and prevent errors, omissions, or alterations in data entry, processing, or transmission. Check totals can also help identify and correct data discrepancies or anomalies. Therefore, check totals are the most useful IT controls in mitigating the risk associated with inaccurate data. The other options are not the best answers because they do not directly address the risk of inaccurate data. Encrypted storage of data is an IT control that protects the confidentiality and integrity of data by preventing unauthorized access or modification. However, encryption does not ensure the accuracy or validity of the data itself. Links to source data are IT controls that provide traceability and transparency of data by allowing users to access or view the original data from which the derived or aggregated data is obtained. However, links to source data do not verify or correct the data quality or consistency. Audit trails for updates and deletions are IT controls that record the history and changes of data by capturing the date, time, user, and action performed on the data. Audit trails can help monitor and review the data activities and transactions, but they do not prevent or detect the data errors or inaccuracies. References = CRISC Review Manual, pages 164-1651; CRISC Review Questions, Answers & Explanations Manual, page 722

According to the CRISC Review Manual (Digital Version), periodically reviewing controls per the risk treatment plan would best help to ensure that identified risk is efficiently managed, as it involves verifying the effectiveness and efficiency of the implemented risk response actions and identifying any gaps or changes in the risk profile. Periodically reviewing controls per the risk treatment plan helps to:

Confirm that the controls are operating as intended and producing the desired outcomes

Detect any deviations, errors, or weaknesses in the controls and their performance

Evaluate the adequacy and appropriateness of the controls in relation to the current risk environment and the organization’s risk appetite and risk tolerance

Recommend and implement corrective actions or improvement measures to address any issues or deficiencies in the controls

Update the risk register and the risk treatment plan to reflect the current risk status and the residual risk levels

References = CRISC Review Manual (Digital Version), Chapter 4: IT Risk Monitoring and Reporting, Section 4.1: IT Risk Monitoring, pp. 215-2161