Question 430
At fictional Portside Payments, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A payment service encrypts records but has no key version metadata or operational method to revoke a compromised encryption key. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Encryption protection depends on key management lifecycle and access governance, not algorithms alone. Rotation exercises show old records remain decryptable under controlled policy while new writes use the approved key version.
Incorrect Answers
This response concerns weak password hashing. Here, a payment service encrypts records but has no key version metadata or operational method to revoke a compromised encryption key. The confirming evidence is: Rotation exercises show old records remain decryptable under controlled policy while new writes use the approved key version.
Focusing on data retention enforcement would leave this problem unresolved: A payment service encrypts records but has no key version metadata or operational method to revoke a compromised encryption key.
Secrets embedded in mobile builds concerns another aspect of the problem. Encryption protection depends on key management lifecycle and access governance, not algorithms alone.