Full Access Isaca CDPSE Tutorials

The value proposition of a PIA is not understood by management is the greatest obstacle to conducting a PIA, as it may result in lack of support, funding, resources or commitment for the PIA process and outcomes. Management may not appreciate or recognize the benefits of a PIA, such as enhancing privacy protection, reducing privacy risks and costs, increasing customer trust and satisfaction, and complying with privacy laws and regulations. Management may also perceive a PIA as a burden, a delay or a hindrance to the system or project development and delivery. The other options are not as significant as the value proposition of a PIA is not understood by management as obstacles to conducting a PIA. Conducting a PIA requires significant funding and resources is an obstacle to conducting a PIA, but it may be overcome by demonstrating the return on investment or the cost-benefit analysis of a PIA. PIAs need to be performed many times in a year is an obstacle to conducting a PIA, but it may be mitigated by adopting a scalable or modular approach to PIAs that can be tailored to different types or levels of systems or projects. The organization lacks knowledge of PIA methodology is an obstacle to conducting a PIA, but it may be resolved by acquiring or developing the necessary skills, tools or guidance for performing PIAs1, p. 67-68 References: 1: CDPSE Review Manual (Digital Version)

 Including privacy requirements in vendor contracts is the best way to ensure privacy considerations are included when working with vendors because it establishes the obligations, expectations and responsibilities of both parties regarding the protection of personal data. It also provides a legal basis for enforcing compliance and resolving disputes. Including privacy requirements in the request for proposal (RFP) process, monitoring privacy-related service level agreements (SLAs) and requiring vendors to complete privacy awareness training are helpful measures, but they do not guarantee that vendors will adhere to the privacy requirements or that they will be held accountable for any violations.

References:

• CDPSE Review Manual (Digital Version), Domain 1: Privacy Governance, Task 1.7: Participate in the management and evaluation of contracts, service levels and practices of vendors and other external parties1
• CDPSE Certified Data Privacy Solutions Engineer All-in-One Exam Guide, Chapter 2: Privacy Governance, Section: Vendor Management2

A mobile application implementation should meet the organization’s data security standards by ensuring that the application does not contain any vulnerabilities, errors or malicious code that could compromise the confidentiality, integrity or availability of the data. An automatic dynamic code scan is a technique that analyzes the application code while it is running to detect and report any security issues or defects. An automatic dynamic code scan can help to identify and fix any potential data security risks before the application is deployed. The other options are not sufficient to ensure data security standards. UAT is a process of verifying that the application meets the user requirements and expectations, but it does not necessarily test for data security. Data classification is a process of categorizing data according to its sensitivity and value, but it does not ensure that the data is protected by the application. A PIA is a process of identifying and evaluating the privacy impacts of a system or project that involves personal data, but it does not ensure that the system or project meets data security standards. , p. 89-90 References: : CDPSE Review Manual (Digital Version)