Question 540
During an approved configuration change involving the research institute tenancy, the cloud security team observes: Production infrastructure code can be changed without peer review. 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: model provider insiders and tenant impersonation as trust-boundary threats” is a recurring check for another risk: Cloud threat modeling ignores privileged insiders and tenant boundary abuse. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: require version-controlled approved infrastructure promotion”.
“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: require version-controlled approved infrastructure promotion”.
“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: require version-controlled approved infrastructure promotion”.