PCI 3DS Core Security Standard P2-3.5.1: P2-3.5.1 Availability mechanisms against loss of 3DS processing

What else in your programme already covers this

This control maps to 2 controls across 2 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 2 Requirement P2-3: Protect 3DS systems and applications – PCI 3DS Core Security Standard

• P2-3.1.1 P2-3.1.1 ACS and DS traffic limited to 3DS functions
• P2-3.1.2 P2-3.1.2 ACS and DS reachable only through approved interfaces
• P2-3.2.1 P2-3.2.1 Configurations and security documentation protected
• P2-3.3.1 P2-3.3.1 Production applications protected from unauthorised change
• P2-3.3.2 P2-3.3.2 Application protection mechanisms monitored and maintained
• P2-3.3.3 P2-3.3.3 APIs to the 3DE identified, defined and tested
• P2-3.3.4 P2-3.3.4 APIs exposed to untrusted networks protected
• P2-3.4.1 P2-3.4.1 Only required HTTP methods accepted