Free CRISC Exam Braindumps
Certified in Risk and Information Systems Control Questions 821–825 (page: 166)

Updated On: 10-Feb-2026

Controls should be defined during the design phase of system development because:

  1. it is more cost-effective to determine controls in the early design phase.
  2. structured analysis techniques exclude identification of controls.
  3. structured programming techniques require that controls be designed before coding begins.
  4. technical specifications are defined during this phase.

Answer(s): A

Explanation:

Controls are the mechanisms or procedures that ensure the security, reliability, and quality of an IT system or process. Controls can be preventive, detective, or corrective, and can be implemented at various levels, such as physical, logical, administrative, or technical. Controls should be defined during the design phase of system development because it is more cost-effective to determine controls in the early design phase. The design phase is the stage where the system requirements are translated into a detailed technical plan, which includes the system architecture, database structure, user interface, and system components. The design phase also defines the system objectives, goals, and performance criteria. Defining controls during the design phase can help ensure that the controls are aligned with the system requirements and objectives, and that they are integrated into the system design from the start. Defining controls during the design phase can also help avoid or reduce the costs and risks associated with implementing controls later in the development or operation phases, such as rework, delays, errors, failures, or breaches. References = THE SYSTEM DEVELOPMENT LIFE CYCLE (SDLC), p. 2-3, System Development LifeCycle - GeeksforGeeks, 7.3: Systems Development Life Cycle - Engineering LibreTexts, What Is SDLC? 7 Phases of System Development Life Cycle - Intetics.



Which of the following is the MOST appropriate key risk indicator (KRI) for backup media that is recycled monthly?

  1. Time required for backup restoration testing
  2. Change in size of data backed up
  3. Successful completion of backup operations
  4. Percentage of failed restore tests

Answer(s): D

Explanation:

The most appropriate key risk indicator (KRI) for backup media that is recycled monthly is the percentage of failed restore tests. A KRI is a metric that measures the likelihood or impact of a risk, and provides an early warning signal of a potential risk event. The percentage of failed restore tests is a KRI that reflects the quality and reliability of the backup media, and indicates the possibility of data loss or corruption. A high percentage of failed restore tests would suggest that the backup media is not functioning properly, and that the risk of data unavailability is increasing. Therefore, this KRI would help the risk practitioner to monitor the risk and take corrective actions as needed. References = Risk and Information Systems Control Study Manual, 7th Edition, Chapter 5, Section 5.2.2, page 235.



An organization has decided to outsource a web application, and customer data will be stored in the vendor's public cloud. To protect customer data, it is MOST important to ensure which of the following?

  1. The organization's incident response procedures have been updated.
  2. The vendor stores the data in the same jurisdiction.
  3. Administrative access is only held by the vendor.
  4. The vendor's responsibilities are defined in the contract.

Answer(s): D

Explanation:

Outsourcing a web application and storing customer data in the vendor's public cloud involves transferring some of the organization's data processing and storage functions to a third-party service provider. This can bring benefits such as cost savings, scalability, and flexibility, but it also introduces risks such as data breaches, unauthorized access, compliance violations, and loss of control12.
To protect customer data, it is most important to ensure that the vendor's responsibilities are defined in the contract. A contract is a legally binding agreement that specifies the terms and conditions of the outsourcing relationship, such as the scope, duration, quality, and cost of the services, as well as the rights and obligations of both parties. A contract should also address the following aspects of data protection :
Data ownership: The contract should clearly state that the organization retains the ownership and control of its customer data, and that the vendor has no rights to use, disclose, or retain the data for any purpose other than providing the agreed services.

Data security: The contract should define the minimum security standards and controls that the vendor must implement and maintain to protect the customer data from unauthorized or accidental access, use, disclosure, modification, or destruction. The contract should also specify the security certifications or audits that the vendor must comply with or undergo to demonstrate its security posture.
Data privacy: The contract should ensure that the vendor complies with the applicable data privacy laws and regulations that govern the collection, processing, and transfer of customer data, such as the General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA). The contract should also require the vendor to obtain the consent of the customers before collecting or sharing their data, and to respect their rights to access, correct,

delete, or restrict their data.
Data breach notification: The contract should establish the procedures and timelines for the vendor to notify the organization and the relevant authorities in the event of a data breach or security incident that affects the customer data. The contract should also define the roles and responsibilities of both parties in responding to and resolving the incident, as well as the remedies and penalties for the vendor's failure or negligence. Data backup and recovery: The contract should outline the backup and recovery policies and practices that the vendor must follow to ensure the availability and integrity of the customer data in case of a disaster or system failure. The contract should also specify the frequency and format of the backups, the location and security of the backup storage, and the testing and restoration procedures.
Data retention and disposal: The contract should stipulate the retention period and disposal method for the customer data, in accordance with the organization's data retention policy and the legal or regulatory requirements. The contract should also require the vendor to return or destroy the customer data at the end of the contract or upon the organization's request, and to provide proof of the data deletion.
By defining the vendor's responsibilities in the contract, the organization can ensure that the customer data is protected in a consistent and compliant manner, and that the vendor is accountable and liable for any data protection issues or breaches that may arise from the outsourcing arrangement .
The other options are not as important as defining the vendor's responsibilities in the contract, because they do not address the core issue of establishing a clear and enforceable data protection framework between the organization and the vendor. Updating the organization's incident response procedures, which are the plans and actions to be taken in the event of a data breach or security incident, may help to mitigate the impact and consequences of such events, but it does not prevent or reduce the likelihood of them occurring in the first place. Storing the data in the same jurisdiction, which means keeping the data within the same geographic or legal boundaries as the organization, may help to avoid some of the data privacy and sovereignty challenges that arise from cross-border data transfers, but it does not guarantee the security and confidentiality of the data. Restricting the administrative access to the vendor, which means limiting the ability to view, modify, or delete the data to the vendor's personnel only, may help to reduce the risk of unauthorized or accidental access by the organization's staff, but it does not ensure that the vendor's staff are trustworthy and competent, and it may also impair the organization's oversight and control over the data.
References = Consumer data protection and privacy | McKinsey, 9 Tips for Protecting Consumer Data (& Why It's Important to Keep It ..., [Outsourcing Contracts: Key Issues and Best Practices], [Data Protection in Cloud Services: A Guide for Businesses], [Incident Response Planning: Best Practices for Businesses], [Data Localization: What is it and Why is it Important?], [Administrative Access: Definition, Risks, and Best Practices]



When reviewing management's IT control self-assessments, a risk practitioner noted an ineffective control that links to several low residual risk scenarios.
What should be the NEXT course of action?

  1. Assess management's risk tolerance.
  2. Recommend management accept the low-risk scenarios.
  3. Propose mitigating controls
  4. Re-evaluate the risk scenarios associated with the control

Answer(s): B

Explanation:

IT control self-assessments are techniques that involve identifying and evaluating the effectiveness and efficiency of the IT controls that are designed and implemented to mitigate the IT risks, by the managers and staff within the organization12. An ineffective control is a control that does not achieve its intended objective or purpose, or does not operate as designed or expected34.
A low residual risk scenario is a situation or occurrence that has a low likelihood and impact of affecting the organization's objectives, performance, or value creation, after considering the existing controls and their effectiveness56.
The next course of action when reviewing management's IT control self-assessments and noting an ineffective control that links to several low residual risk scenarios is to recommend management accept the low-risk scenarios, which is a risk response strategy that involves acknowledging and tolerating the level of risk exposure, and not taking any further action to reduce or eliminate it78.
Recommending management accept the low-risk scenarios is the next course of action because it is the most cost-effective and reasonable option, given that the level of risk exposure is low andacceptable, and the cost and effort of implementing or improving the control may outweigh the potential benefits or value78.

Recommending management accept the low-risk scenarios is also the next course of action because it is consistent with the risk management process and objectives, which are to identifyand address the risks that may affect the achievement of the organization's goals and the delivery of value to the stakeholders, and to optimize the balance between risk and reward78.
The other options are not the next course of action, but rather possible alternatives or steps that may be considered or followed in different circumstances or scenarios. For example:
Assessing management's risk tolerance is a step that involves determining and communicating the acceptable or tolerable level of risk exposure for the organization or its business units, based on the organization's risk appetite, criteria, and objectives78. However,

this stepis not the next course of action because it is usually done before or during the risk assessment process, and not after noting an ineffective control that links to several low residual risk scenarios78.
Proposing mitigating controls is a course of action that involves suggesting or recommending additional or alternative controls that can reduce or eliminate the level of risk exposure, and improve the effectiveness and efficiency of the risk management process78. However, this course of action is not the next course of action because it is not necessary or appropriate for low residual risk scenarios, as the cost and effort of implementing or improving the controls may outweigh the potential benefits or value78.
Re-evaluating the risk scenarios associated with the control is a course of action that involves revising and updating the likelihood and impact of the risk scenarios, and the level of risk exposure or tolerance for the organization, based on the current or changed conditions or factors that influence the risk landscape78. However, this course of action is not the next course of action because it is not required or relevant for low residual risk scenarios, as the level of risk exposure is already low and acceptable, and the ineffective control does not significantly affect the risk assessment78. References =
1: Control Self Assessments - PwC1
2: Control self-assessment - Wikipedia2
3: Ineffective Controls: What They Are and How to Identify Them3
4: Ineffective Controls: What They Are and How to Identify Them4
5: Residual Risk - Definition and Examples5
6: Residual Risk: Definition, Formula & Management6
7: Risk IT Framework, ISACA, 2009
8: IT Risk Management Framework, University of Toronto, 2017



Which of the following will BEST help in communicating strategic risk priorities?

  1. Heat map
  2. Business impact analysis (BIA)
  3. Balanced Scorecard
  4. Risk register

Answer(s): A

Explanation:

The best tool for communicating strategic risk priorities is a heat map. A heat map is a graphical representation of the risk profile of an enterprise, showing the likelihood and impact of various risks on a matrix. A heat map can help to highlight the most significant risks that require attention, as well as the risk appetite and tolerance levels of the enterprise.

A heat map can also facilitate the comparison of risks across different business units, processes, or objectives, and enable the communication of risk information to stakeholders in a clear and concise manner. References = Risk and Information Systems Control Study Manual, 7th Edition, Chapter 5, Section 5.3.1, page 240.



Viewing page 166 of 380
Viewing questions 826 - 830 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!