Public-facing web applications must be protected by an automated technical control that constantly spots and stops web-based attacks and that, at minimum: is placed ahead of the public-facing web applications and configured to find and block web-based attacks; runs actively and is kept updated where relevant; produces audit logs; and is set either to block web-based attacks or to raise an alert that is investigated immediately. It applies to all entities with public-facing web applications. Applicability: this newer requirement takes the place of 6.4.1 from the date it became effective. Objective under the customized approach: public-facing web applications are defended against malicious attacks in real time. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 32 controls across 15 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.
PCI DSS 4.0 6.4.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 32 it maps to, and the evidence behind each claim, over MCP and REST.