EMV 3-D Secure (3DS) - Payment Authentication Protocol
Security requirements: links and functions (chapter 6) – EMV 3-D Secure (3DS) - Payment Authentication Protocol

EMV 3-D Secure (3DS) - Payment Authentication Protocol 6.1.2-3: 6.1.2-3 Links b and c: 3DS Server to DS and DS to ACS

The 3DS Server to DS links for AReq/ARes and RReq/RRes and the DS to ACS links for the same pairs use TLS with the Annex D cipher suites and mutual authentication, with X.509 certificates for both parties signed by the DS certificate authority, the 3DS Server selecting the right certificate where it links to several DSs.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 3 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.

PCI 3DS Core Security Standard · 3 controls

  • 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-6.1.8 P2-6.1.8 Trusted CA for all 3DS certificates

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 Security requirements: links and functions (chapter 6) – EMV 3-D Secure (3DS) - Payment Authentication Protocol

Query this from an agent

The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll EMV 3-D Secure (3DS) - Payment Authentication Protocol controls