PCI DSS 4.0 6.5.4: 6.5.4 Separate roles between production and pre-production
Roles and functions must be divided between production and pre-production environments so that accountability exists and only changes that have been reviewed and approved reach production. It applies to all entities. Applicability: where staff numbers are small and individuals hold several roles, the same aim can be met through extra procedural controls that create accountability; as an illustration, a developer could hold an elevated administrator account in development but a separate user-level account in production for developer tasks. Objective under the customized approach: job roles and accountability that distinguish pre-production work from production work are defined and managed to reduce the risk of unauthorised, unintentional or inappropriate actions.
This control maps to 43 controls across 19 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.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 6.5.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.