CDPSE VCE Exam Download

Storing tokens of PII directly in database fields undermines the security of tokenization and risks re-identification, making it the most concerning issue. Shared drives (A) and lack of labels (B) are governance gaps, and limited third-party access (C) can be controlled contractually, but token misuse (D) poses direct privacy risk.

“Improper token storage can compromise de-identification, reintroducing privacy risk.”

De-identification is a technique that removes or modifies direct and indirect identifiers in a data set to prevent or limit the identification of the data subjects. De-identification reduces the risk of re-identification and thus limits the organization’s potential exposure in the event of consumer data loss. De-identification also maintains the traceability of the data by preserving some characteristics or patterns of the original data that can be used for analysis or research purposes. The other options are not effective ways to limit exposure and maintain traceability1, p. 75-76 References: 1: CDPSE Review Manual (Digital Version)

The best testing method to identify and review the application’s runtime modules is dynamic application security testing (DAST). DAST is a testing technique that analyzes the application’s behavior and functionality during its execution. DAST can detect security and privacy vulnerabilities that are not visible in the source code, such as injection attacks, cross-site scripting, broken authentication, sensitive data exposure, or improper error handling. DAST can also simulate real-world attacks and test the application’s response and resilience. DAST can provide a comprehensive and realistic assessment of the application’s security and privacy posture in the pre-production environment. References:

[ISACA Glossary of Terms]

[OWASP Top 10 Web Application Security Risks]

[ISACA CDPSE Review Manual, Chapter 2, Section 2.4.2]

[ISACA Journal, Volume 6, 2018, “Dynamic Application Security Testing”]

The best way to safeguard the encryption keys is to ensure that they are stored in a cryptographic vault. A cryptographic vault is a secure hardware or software module that provides cryptographic services and protects the keys from unauthorized access, modification, or disclosure. A cryptographic vault can also provide other functions, such as key generation, key backup, key rotation, key destruction, and key auditing. A cryptographic vault can enhance the security and privacy of the encrypted data by preventing key compromise, leakage, or misuse. A cryptographic vault can also comply with the security standards and best practices for key management, such as the ISO/IEC 27002, NIST SP 800-57, or PCI DSS. References:

[ISACA Glossary of Terms]

[ISACA CDPSE Review Manual, Chapter 3, Section 3.3.3]

[ISACA Journal, Volume 4, 2019, “Key Management in the Multi-Cloud Environment”]

[ISACA CDPSE Review Manual, Chapter 3, Section 3.3.4]