PCI 3DS Core Security Standard P1-3.3.4: P1-3.3.4 Rollback prepared for every change

What else in your programme already covers this

This control maps to 1 controls across 1 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.

Other controls in Part 1 Requirement P1-3: Develop and maintain secure systems – PCI 3DS Core Security Standard

• P1-3.1.1 P1-3.1.1 Secure development lifecycle policy and procedures
• P1-3.1.2 P1-3.1.2 Developers trained in secure development
• P1-3.1.3 P1-3.1.3 Development procedures address common coding weaknesses
• P1-3.1.4 P1-3.1.4 Security testing during development using documented methods
• P1-3.1.5 P1-3.1.5 Testing surfaces defects and vulnerabilities
• P1-3.1.6 P1-3.1.6 Defects and vulnerabilities fixed before release
• P1-3.1.7 P1-3.1.7 Management signs off test results before release
• P1-3.2.1 P1-3.2.1 Build and configuration management policy and procedures