Web applications sit behind a suitable web application firewall that monitors and filters traffic to and from the application against attacks such as cross-site request forgery, cross-site scripting, file inclusion and SQL injection. Data input from users is accepted only at designated locations. All client-supplied data is validated, including user-provided content and browser-supplied headers such as referrer and user agent. The application does not allow special characters, in particular those used in SQL queries, in its inputs. Everything sent by a client and displayed on a page is HTML-encoded so that it renders as text rather than as markup or script.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.