Live PANs must not be used in pre-production environments, unless those environments are inside the CDE and protected in line with every applicable PCI DSS requirement. A live PAN is a valid number issued by or for a payment brand, as opposed to a test number; the guidance notes that an expired card's PAN is often reissued with a new expiry date, and that it falls to the entity to confirm a PAN cannot transact or create fraud risk before treating it as out of scope. It applies to all entities. Customized approach objective: live PANs cannot exist in pre-production environments that sit outside the CDE.
This control maps to 23 controls across 11 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.5.5 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 23 it maps to, and the evidence behind each claim, over MCP and REST.