PCI 3DS Core Security Standard
Part 2 Requirement P2-5: Protect 3DS data – PCI 3DS Core Security Standard

PCI 3DS Core Security Standard P2-5.4.2: P2-5.4.2 Strong cryptography for stored 3DS sensitive data

Wherever storage of 3DS sensitive data is permitted, it is protected with strong cryptography. Technical FAQ Q1 (April 2021) adds that a static Authentication Value had to be encrypted before any permitted storage, while a single-use or already strongly encrypted value might not need encrypting again; Data Matrix v1.3 has since removed the Authentication Value from the sensitive-data table. The assessor examines documentation on protection methods and observes controls and configurations.

Maintained by Gerard Blokdyk

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.

PCI DSS 4.0 · 1 control

  • 3.3.2 3.3.2 Pre-authorization SAD stored electronically is strongly encrypted

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

Query this from an agent

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

MCP endpointAll PCI 3DS Core Security Standard controls