Question 240
During a privacy impact assessment involving the international collaboration tenant, the cloud security team observes: Code is promoted directly to production without a security release gate. 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: integrate security design reassessment into sprint planning” is a recurring check for another risk: Threat models are not revisited during fast iterative feature releases. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: establish SDLC test and approval stages before deployment”.
“Periodically verify, document, and enforce this requirement: use parameterized database queries with safe input handling” is a recurring check for another risk: Cloud code builds SQL queries by concatenating untrusted request strings. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: establish SDLC test and approval stages before deployment”.
“Periodically verify, document, and enforce this requirement: pin vetted signed versions and verify package provenance” is a recurring check for another risk: An open-source dependency is taken over by an untrusted maintainer. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: establish SDLC test and approval stages before deployment”.