PCI 3DS Core Security Standard P2-5.2.1: P2-5.2.1 Strong cryptography for 3DS sensitive data in transit

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 2 Requirement P2-5: Protect 3DS data – PCI 3DS Core Security Standard

• P2-5.1.1 P2-5.1.1 3DS data lifecycle policies and procedures
• P2-5.1.2 P2-5.1.2 3DS data kept only as long as needed, then purged securely
• P2-5.2.2 P2-5.2.2 No fallback to insecure protocols
• P2-5.3.1 P2-5.3.1 TLS between 3DS components uses only allowed cipher suites
• P2-5.3.2 P2-5.3.2 No EMVCo-unsupported cipher suites offered
• P2-5.3.3 P2-5.3.3 No rollback to unapproved algorithms or key sizes
• P2-5.3.4 P2-5.3.4 TLS configurations monitored for change
• P2-5.4.1 P2-5.4.1 Stored 3DS sensitive data limited to permitted elements