Ace Your CRISC Isaca Certification Exam

The most helpful information to review when determining a system’s criticality is the associated business impact analysis (BIA). A BIA is a process of identifying and evaluating the potential effects of disruptions to the organization’s critical business functions and processes. A BIA can help to determine the system’s criticality by assessing its impact on the organization’s objectives, performance, and value. Process flow, service level agreement (SLA), and system architecture are other possible information sources, but they are not as helpful as the BIA. References = ISACA Certified in Risk and Information Systems Control (CRISC) Certification Exam Question and Answers, question 4; CRISC Review Manual, 6th Edition, page 153.

 The best recommendation to address the situation where personal information from the production environment is required for testing purposes in non-production environments is to de-identify data before being transferred to the test environment. De-identification is the process of removing or modifying any personally identifiable information (PII) or other sensitive data from the data sets, such as names, addresses, phone numbers, email addresses, etc., so that the data cannot be traced back to specific individuals. De-identification protects the privacy and confidentiality of the data, while still allowing for testing, analysis, or training purposes. Enabling data encryption, preventing the use of production data, and enforcing multi-factor authentication are also useful measures, but they do not eliminate the risk of data breaches or unauthorized access to PII. References = Risk and Information Systems Control Study Manual, Chapter 3, Section 3.3.1, page 3-21.

Conducting vulnerability scans is the best way for a risk practitioner to validate the effectiveness of a patching program. Vulnerability scans are automated tools that identify and report on the vulnerabilities in a system or network, such as missing patches, misconfigurations, or outdated software. Vulnerability scans can help the risk practitioner to verify that the patches have been applied correctly and consistently, and that there are no remaining or new vulnerabilities that need to be addressed. Conducting penetration testing, interviewing IT operations personnel, and reviewing change control board documentation are also useful methods to evaluate the patching program, but they are not as comprehensive, objective, or timely as vulnerability scans. References = Risk and Information Systems Control Study Manual, Chapter 2, Section 2.3.3, page 2-28.

The main benefit of using a top-down approach to develop risk scenarios is that it establishes the relationship between risk events and organizational objectives. A top-down approach is a method of risk identification and analysis that starts with the organization’s strategic objectives and then identifies the potential risk events that could affect or prevent the achievement of those objectives. A top-down approach helps to establish the relationship between risk events and organizational objectives, because it links the risk scenarios to the organization’s mission, vision, values, and strategy, and it prioritizes the risk scenarios based on their impact and relevance to the organization’s objectives. A top-down approach also helps to align and communicate the risk scenarios with the organization’s stakeholders, such as the board, management, and business units, and to facilitate the risk response and monitoring activities. The other options are not the main benefit of using a top-down approach, although they may be part of or derived from the top-down approach. Describing risk events specific to technology used by the enterprise, using hypothetical and generic risk events specific to the enterprise, and helping management and the risk practitioner to refine risk scenarios are all activities or outcomes that could be performed or achieved by using a top-down approach, but they are not the primary purpose or result of the top-down approach. References = Risk and Information Systems Control Study Manual, Chapter 4, Section 4.2.1, page 4-13.