Question 460
Following the issue — A CDN rule caches sensitive authenticated response content at the edge due to an overly broad cache policy. — the team takes this action: Correct cache behavior to avoid storing personalized or sensitive responses in shared caches. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Audit cache-control and route rules when changing Front Door or CDN behavior. This mitigates the control weakness because: Caching decisions affect confidentiality independently from HTTPS transport encryption. Keep the intervention, Correct cache behavior to avoid storing personalized or sensitive responses in shared caches., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Route enterprise network exceptions through the central network security owner” addresses a different recurring failure: A centrally enforced Deny in the network manager security administration can supersede subordinate security controls. For the condition in this question, maintain “Audit cache-control and route rules when changing Front Door or CDN behavior” because caching decisions affect confidentiality independently from HTTPS transport encryption.
This safeguard is for the dependency described by: Distinct PaaS subresources can have separate private link endpoint and DNS requirements. The continuing risk here is determined by: Caching decisions affect confidentiality independently from HTTPS transport encryption. The targeted safeguard is “Audit cache-control and route rules when changing Front Door or CDN behavior”.
“Include IP forwarding and appliance health in route-change validation” addresses a different recurring failure: A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination. For the condition in this question, maintain “Audit cache-control and route rules when changing Front Door or CDN behavior” because caching decisions affect confidentiality independently from HTTPS transport encryption.