Every script on the payment page that is loaded and run in the consumer's browser must be controlled such that: a method is in place to confirm that each script is authorised; a method is in place to ensure the integrity of each script; and an inventory of all such scripts is kept, with a written business or technical justification explaining why each one is needed. It applies to all entities with payment pages. Applicability: covers scripts loaded from the entity's own environment and from third and fourth parties, and scripts on the entity's pages that embed a TPSP or payment processor payment page or form (for example, via iframes); it does not cover scripts inside the TPSP's or processor's embedded page or form, which that TPSP or processor must manage under this requirement. Objective under the customized approach: unauthorised code cannot run in the payment page as the consumer's browser renders it. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 39 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.3 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 39 it maps to, and the evidence behind each claim, over MCP and REST.