Question 180
During a privacy impact assessment involving the retail payment infrastructure, the cloud security team observes: Archived customer datasets were never reclassified after collection. The decision must preserve authorized security and availability requirements. Which repeatable governance control BEST prevents a recurrence?
Explanation
Correct Answer
Repeatable verification of the specific remediation prevents the same control gap from silently reappearing after deployments or changes.
Incorrect Answers
“Periodically verify, document, and enforce this requirement: identify systems of record and set separate retention for derived copies” is a recurring check for another risk: An application confuses temporary cache records with authoritative customer data. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: apply current classification across all data lifecycle stages and archives”.
“Periodically verify, document, and enforce this requirement: assess linkage risk and apply stronger aggregation or differential privacy” is a recurring check for another risk: A supposedly anonymous health dataset can be re-identified by indirect attributes. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: apply current classification across all data lifecycle stages and archives”.
“Periodically verify, document, and enforce this requirement: replace sensitive identifiers with tokens mapped in a protected vault” is a recurring check for another risk: Real customer identifiers are copied into development databases. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: apply current classification across all data lifecycle stages and archives”.