Question 660
During an architecture review involving the transport logistics service, the cloud security team observes: CASB monitoring misses sensitive uploads through unsanctioned SaaS. 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: validate signed token issuer audience expiry and scopes” is a recurring check for another risk: A service accepts tokens without checking issuer or audience. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: expand sanctioned and unsanctioned cloud application visibility”.
“Periodically verify, document, and enforce this requirement: integrate software composition analysis in the build pipeline” is a recurring check for another risk: CI tests functionality but does not detect vulnerable third-party packages. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: expand sanctioned and unsanctioned cloud application visibility”.
“Periodically verify, document, and enforce this requirement: assign contract security duties and customer release approval ownership” is a recurring check for another risk: Outsourced developers deliver an application with no customer security acceptance. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: expand sanctioned and unsanctioned cloud application visibility”.