The provider must implement controls ensuring every customer is permitted to access only its own cardholder data and its own cardholder data environment (CDE), never another tenant's. Guidance example: in an IaaS-style offering the customer CDE may include virtual servers, virtual network devices, operating systems, files and memory that the customer configures and manages itself. Applies to multi-tenant service providers. Customized approach objective: one customer is unable to reach any other customer's environment.
PCI DSS 4.0 A1.1.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 0 it maps to, and the evidence behind each claim, over MCP and REST.