PCI 3DS Core Security Standard
Part 2 Requirement P2-6: Cryptography and key management – PCI 3DS Core Security Standard

PCI 3DS Core Security Standard P2-6.1.2: P2-6.1.2 HSM for specified keys at ACS and DS

At the ACS and DS, all key-management activity for the cryptographic keys the PCI 3DS Data Matrix specifies (Table 2 in v1.3: the ACS private key for signed content and the DS private key used to decrypt SDK-encrypted data) takes place in an HSM whose validation is either at Level 3 or above overall under FIPS 140-2, or PCI PTS HSM approved. The assessor examines the key-management procedures and interviews personnel.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 3 controls across 3 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • 6.2.1-2 6.2.1-2 Functions H and I: SDK authenticity and SDK encryption to the DS

PCI DSS 4.0 · 1 control

  • 3.6.1.2 3.6.1.2 Permitted storage forms for secret and private keys

PCI PIN Security · 1 control

  • 1-3 PCI PIN 1-3

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-6: Cryptography and key management – PCI 3DS Core Security Standard

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.