How should you prevent and fix this vulnerability?

You are on your company’s development team. You noticed that your web application hosted in staging on GKE dynamically includes user data in web pages without first properly validating the inputted data. This could allow an attacker to execute gibberish commands and display arbitrary content in a victim user’s browser in a production environment.

How should you prevent and fix this vulnerability?
A . Use Cloud IAP based on IP address or end-user device attributes to prevent and fix the vulnerability.
B . Set up an HTTPS load balancer, and then use Cloud Armor for the production environment to prevent the potential XSS attack.
C . Use Web Security Scanner to validate the usage of an outdated library in the code, and then use a secured version of the included library.
D . Use Web Security Scanner in staging to simulate an XSS injection attack, and then use a templating system that supports contextual auto-escaping.

Answer: D

Explanation:

There is mention about simulating in Web Security Scanner. "Web Security Scanner cross-site scripting (XSS) injection testing *simulates* an injection attack by inserting a benign test string into user-editable fields and then performing various user actions." https://cloud.google.com/security-command-center/docs/how-to-remediate-web-security-scanner-findings#xss

Reference: https://cloud.google.com/security-scanner/docs/remediate-findings