PCI 3DS Core Security Standard P2-2.4.2: P2-2.4.2 Due diligence before engaging a third party

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-2: Security governance – PCI 3DS Core Security Standard

• P2-2.1.1 P2-2.1.1 Security objectives aligned with business objectives
• P2-2.1.2 P2-2.1.2 Security responsibility and accountability formally assigned
• P2-2.1.3 P2-2.1.3 Responsibility for evolving risks assigned
• P2-2.2.1 P2-2.2.1 Formal risk-management strategy defined
• P2-2.2.2 P2-2.2.2 Risk strategy approved and kept current
• P2-2.3.1 P2-2.3.1 Periodic checks that staff follow security policies
• P2-2.3.2 P2-2.3.2 Security control failures detected and responded to
• P2-2.4.1 P2-2.4.1 Third-party relationship policies and procedures