Free CRISC Exam Braindumps
Certified in Risk and Information Systems Control Questions 651–655 (page: 132)

Updated On: 10-Feb-2026

What is the MAIN benefit of using a top-down approach to develop risk scenarios?

  1. It describes risk events specific to technology used by the enterprise.
  2. It establishes the relationship between risk events and organizational objectives.
  3. It uses hypothetical and generic risk events specific tothe enterprise.
  4. It helps management and the risk practitioner to refine risk scenarios.

Answer(s): B

Explanation:

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.



A rule-based data loss prevention {DLP) tool has recently been implemented to reduce the risk of sensitive data leakage.
Which of the following is MOST likely to change as a result of this implementation?

  1. Risk likelihood
  2. Risk velocity
  3. Risk appetite
  4. Risk impact

Answer(s): A

Explanation:

A rule-based data loss prevention (DLP) tool is a software solution that identifies and helps prevent unsafe or inappropriate sharing, transfer, or use of sensitive data. It can help an organization monitor and protect sensitive information across on-premises systems, cloud- based locations, and endpoint devices. It can also help an organization comply with regulations such as the Health Insurance Portability and Accountability Act (HIPAA) and General Data Protection Regulation (GDPR). A rule-based DLP tool works by comparing content to the organization's DLP policy, which defines how the organization labels, shares,

and protects data without exposing it to unauthorized users. The tool can then apply protective actions such as encryption, access restrictions, and alerts. As a result of implementing a rule-based DLP tool, the most likely change is the reduction of risk likelihood, which is the probability of a risk event occurring. By detecting and preventing data breaches, exfiltration, or unwanted destruction of sensitive data, a rule-based DLP tool can lower the chance of such incidents happening and thus decrease the risk likelihood. The other options are less likely to change as a result of implementing a rule-based DLP tool. Risk velocity is the speed at which a risk event impacts an organization, which depends on factors such as the nature of the threat, the response time, and the recovery process. Risk appetite is the amount and type of risk that an organization is willing to accept in pursuit of its objectives, which depends on factors such as the organization's culture, strategy, and stakeholder expectations. Risk impact is the potential loss or damage that a risk event can cause to an organization, which depends on factors such as the severity of the incident, the extent of theexposure, andthe resilience of the organization.
While a rule-based DLP tool may have some influence on these factors, it is not the primary driver of change for them. References = Risk IT Framework, ISACA, 2022, p. 13



Which of the following is the BEST way to quantify the likelihood of risk materialization?

  1. Balanced scorecard
  2. Threat and vulnerability assessment
  3. Compliance assessments
  4. Business impact analysis (BIA)

Answer(s): B

Explanation:

A threat and vulnerability assessment is a process that identifies and evaluates the potential sources and impacts of risk events on an organization's assets, processes, and objectives. It also estimates the probability of occurrence and the severity of consequences for each risk event. A threat and vulnerability assessment is the best way to quantify the likelihood of risk materialization, as it provides a numerical or qualitative measure of the risk exposure and the level of uncertainty associated with the risk scenarios. References = Risk and Information Systems Control Study Manual, Chapter 2, Section 2.2.2, p. 68-69



A chief information officer (CIO) has identified risk associated with shadow systems being maintained by business units to address specific functionality gaps in the organization'senterprise resource planning (ERP) system.
What is the BEST way to reduce this risk going forward?

  1. Align applications to business processes.
  2. Implementan enterprise architecture (EA).
  3. Define the software development life cycle (SDLC).
  4. Define enterprise-wide system procurement requirements.

Answer(s): B

Explanation:

Shadow systems are IT systems, solutions, devices, or technologies used within an organization without the knowledge and approval of the corporate IT department1. They are often the result ofemployees trying to address specific functionality gaps in the organization's official systems, such as the ERP system. However, shadow systems can pose significant risks to the organization, such as:
Data security and privacy breaches, as shadow systems may not comply with the organization's security policies and standards, or may expose sensitive data to unauthorized parties2.
Data quality and integrity issues, as shadow systems may not synchronize or integrate with the organization's official systems, or may create data inconsistencies or redundancies3. Compliance and regulatory violations, as shadow systems may not adhere to the organization's legal or contractual obligations, or may create audit or reporting challenges4. Cost and resource inefficiencies, as shadow systems may duplicate or conflict with the organization's official systems, or may consume more IT resources than necessary5. The best way to reduce the risk associated with shadow systems is to implement an enterprise architecture (EA), which is a comprehensive framework that defines the structure, processes, principles, and standards of the organization's IT environment6. By implementing an EA, the organization can:
Align the IT systems with the organization's goals and strategy, and ensure that they support the business needs and requirements6.
Establish a governance structure and process for IT decision making, and ensure that all IT systems are approved, monitored, and controlled by the IT department7. Enhance the communication and collaboration between the IT department and the business units, and ensure that the IT systems meet the expectations and preferences of the end users5. Optimize the performance and efficiency of the IT systems, and ensure that they are scalable, flexible, and interoperable6.
References =
Shadow IT: What Are the Risks and How Can You Mitigate Them? - Ekran System How to Reduce Risks of Shadow IT by Applying Governance to Public Clouds ­ BMC

Software | Blogs
What is shadow IT? - Article | SailPoint
The Risks of Shadow IT and How to Avoid Them | SiteSpect Start reducing your organization's Shadow IT risk in 3 steps What is enterprise architecture (EA)? - Definition from WhatIs.com Enterprise Architecture Governance - CIO Wiki



Which of the following should be determined FIRST when a new security vulnerability is made public?

  1. Whether the affected technology is usedwithin the organization
  2. Whether the affected technology is Internet-facing
  3. What mitigating controls are currently in place
  4. How pervasive the vulnerability is within the organization

Answer(s): A

Explanation:

When a new security vulnerability is made public, the first step is to determine whether the affected technology is used within the organization. This will help to assess the impact and exposure of the vulnerability on the organization's assets, processes, and objectives. If the affected technology is not used within the organization, then the vulnerability does not pose a direct threat and no further action is required. However, if the affected technology is used within the organization, then the next steps are to identify the systems and components that are vulnerable, evaluate the severity and likelihood of the vulnerability being exploited, and implement appropriate mitigating controls or remediation actions. References = Risk and Information Systems Control Study Manual, Chapter 5, Section 5.3.2.1, p. 240-241



Viewing page 132 of 380
Viewing questions 656 - 660 out of 1895 questions


Post your Comments and Discuss ISACA CRISC exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!