The provider must confirm with a penetration test, at least once every six months, that the logical separation controls isolating customer environments are effective. Applicability: this separation testing is additional to the penetration tests required by Requirement 11.4.6. Guidance: a good practice is to build temporary mock-up customer environments and try to reach one from another and from the Internet. Objective under the customized approach: the isolation between each customer environment and every other environment is periodically shown to work. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
PCI DSS 4.0 A1.1.4 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 0 it maps to, and the evidence behind each claim, over MCP and REST.