PCI 3DS Core Security Standard

Part 2 Requirement P2-3: Protect 3DS systems and applications – PCI 3DS Core Security Standard

PCI 3DS Core Security Standard P2-3.3.3: P2-3.3.3 APIs to the 3DE identified, defined and tested

Every API that interfaces with the 3DS environment is identified, has its definition documented and is tested to confirm it behaves as expected. The assessor examines network and data-flow diagrams, observes the controls, examines test results and interviews personnel.

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

6.3.2 6.3.2 Inventory of bespoke software and components

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-3: Protect 3DS systems and applications – 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 endpoint All PCI 3DS Core Security Standard controls