Question 120
During a provider control assessment involving the distributed SaaS application, the cloud security team observes: Emergency production firewall changes lack documented approvals. 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: apply problem management to recurring infrastructure failures” is a recurring check for another risk: Repeated incidents are closed without a lasting root-cause correction. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: use an auditable emergency change process and retrospective review”.
“Periodically verify, document, and enforce this requirement: gate maintenance on distributed storage resiliency headroom” is a recurring check for another risk: Storage nodes are shut down without checking recovery capacity. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: use an auditable emergency change process and retrospective review”.
“Periodically verify, document, and enforce this requirement: revoke stolen sessions and rotate affected cloud keys” is a recurring check for another risk: Compromised cloud credentials continue to access live sessions. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: use an auditable emergency change process and retrospective review”.