PCI P2PE
Domain 2: Application Security – PCI P2PE

PCI P2PE 2B-3.1: PCI P2PE 2B-3.1

What does 2B-3.1 require?

The developer fully documents and integration-tests the application on its intended platforms, providing security guidance on how keys and certificates are to be used (which certificates to load, how account-data keys are loaded through the firmware, when to roll keys) and performing final integration testing on the device that finds and fixes residual vulnerabilities from the integration.

Maintained by Gerard BlokdykControl text last updated

Other controls in Domain 2: Application Security – PCI P2PE

Query this from an agent

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