Question 260
During a cloud operations audit involving the retail payment infrastructure, the cloud security team observes: A service accepts tokens without checking issuer or audience. 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: adopt federated SSO with appropriate MFA and lifecycle management” is a recurring check for another risk: Separate cloud services cause password reuse and inconsistent offboarding. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: validate signed token issuer audience expiry and scopes”.
“Periodically verify, document, and enforce this requirement: establish SDLC test and approval stages before deployment” is a recurring check for another risk: Code is promoted directly to production without a security release gate. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: validate signed token issuer audience expiry and scopes”.
“Periodically verify, document, and enforce this requirement: move secrets to managed runtime storage and rotate exposures” is a recurring check for another risk: API signing secrets are committed into source repositories. This question calls for a different recurring safeguard: “Periodically verify, document, and enforce this requirement: validate signed token issuer audience expiry and scopes”.