CRISC Exam Dumps - Certified in Risk and Information Systems Control

According to the CRISC Review Manual1, authorizing user access requests is the process of granting or denying access to IT resources based on the user’s role, responsibilities, and business needs. Authorizing user access requests is a key control accountability that should be retained within the organization, as it helps to ensure that the principle of least privilege is applied, and that the access rights are aligned with the organization’s policies, standards, and risk appetite. Authorizing user access requests also helps to prevent unauthorized access, data leakage, fraud, and other potential risks associated with user access provisioning and termination. Therefore, the best control accountability to retain within the organizationwhen a third-party vendor offers to perform user access provisioning and termination is authorizing user access requests. References = CRISC Review Manual1, page 240.

Monitoring the average time to complete tasks and monthly reporting of the findings during the month-end close process aligns with the definition of a Key Performance Indicator (KPI).

Understanding KPIs:

Performance Measurement:KPIs are used to measure how effectively a company is achieving its key business objectives. Monitoring the average time to complete tasks during the month-end close process provides a performance metric.

Tracking Efficiency:By reporting these findings monthly, management can track the efficiency and performance of the system load capabilities.

Specific Measure:

Task Completion Time:The average time to complete tasks is a specific, measurable indicator of performance. It helps in understanding how well the system handles load and identifies areas for improvement.

Continuous Improvement:Regular monitoring and reporting encourage continuous improvement, which is a core aspect of using KPIs.

A risk practitioner notices a trend of noncompliance with an IT-related control. This indicates that there is a risk of ineffective or inefficient implementation or operation of the control, which may expose the organization to potential threats or losses.

The best way to assist in making a recommendation to management is to assess the degree to which the control hinders business objectives. This means that the risk practitioner should analyze the impact of the control on the performance, productivity, quality, or customer satisfaction of the business processes or functions that are affected by the control.

Assessing the degree to which the control hinders business objectives helps to identify the root causes of noncompliance, the costs and benefits of compliance, and the potential alternatives or improvements for the control. It also helps to communicate the value and importance of the control to the management and the stakeholders, and to obtain their support and commitment for the control compliance.

The other options are not the best ways to assist in making a recommendation to management. They are either secondary or not essential for control compliance.

The references for this answer are:

Risk IT Framework, page 19

Information Technology & Security, page 13

Risk Scenarios Starter Pack, page 11

Assigning accountability to risk owners is the best way to ensure implementation of corrective action plans, because it clarifies the roles and responsibilities of those who are in charge of managing and mitigating the risks. Contracting to third parties, establishing employee awareness training, and setting target dates tocomplete actions are all helpful measures, but they do not guarantee the implementation of corrective action plans without accountability. References = Risk and Information Systems Control Study Manual, Chapter 3, Section 3.4.3, page 105

IT disaster recovery point objectives (RPOs) should be based on the:

B. maximum tolerable loss of data.

RPOs are determined by how much data loss an organization can withstand in the event of a disaster. It’s a measure of the maximum age of files that an organization must recover from backup storage for normal operations to resume after a disaster. Therefore, RPOs are directly related to the maximum tolerable loss of data.

 Risk appetite is the amount and type of risk that an organization is willing to accept in pursuit of its objectives. Risk appetite can be expressed in qualitative or quantitative terms, and can vary depending on the context and the stakeholder. Risk appetite should be defined and communicated by the senior management or the board of directors, and should guide the risk management decisions and actions throughout the organization. When a project team has accepted a risk outside the established risk appetite, the risk practitioner’s best course of action is to escalate the risk decision to the project sponsor for review, meaning that the risk practitioner should report the risk acceptance and its rationale to the project sponsor, who is the person or group that provides the resources and support for the project, and is accountable for its success. The project sponsor should review the risk decision and determine whether it is aligned with the organization’s objectives and strategy, and whether it requires any further approval oraction. References = Risk and Information Systems Control Study Manual, Chapter 1, Section 1.3.1, p. 25-26

The percentage of unpatched DMZ servers is a critical KCI for preventing cyber risk events on external-facing infrastructure. Unpatched servers are vulnerable to exploitation, and monitoring this indicator helps ensure timely application of security updates, reducing the risk of successful attacks.