PCI DSS 4.0 6.5.3: 6.5.3 Separate pre-production from production
Pre-production environments, such as development, test and user acceptance testing, must be kept apart from production environments, and that separation must be enforced using access controls. The guidance adds that separation can be logical or physical and is still needed where production infrastructure supports testing or development. The aim is to stop weaknesses created during development and testing, where environments change constantly and are often less hardened, from reaching live systems. It applies to all entities. Objective under the customized approach: pre-production environments cannot bring risks or vulnerabilities into production environments.
This control maps to 53 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 6.5.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.