A multi-tenant service provider must implement logical separation so that: (1) the provider itself cannot reach into any customer environment unless authorized, and (2) customers cannot reach into the provider's own environment unless authorized. Guidance: tenant environments should be isolated from one another and from the provider's infrastructure; customer-facing areas such as billing or configuration portals should be kept apart from the provider's private environment; and provider access to customer environments is handled under Requirement 8.2.3. Objective under the customized approach: the provider's environment is closed to customers, and customer environments are closed to the provider without authorization. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
PCI DSS 4.0 A1.1.1 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.