PCI P2PE
Domain 5: P2PE Cryptographic Key Operations and Device Management – PCI P2PE

PCI P2PE 32-8: PCI P2PE 32-8

What does 32-8 require?

Distributed KIF functions that generate and transfer keys talk to each other only over mutually authenticated channels, and each key transfer between them satisfies Control Objective 3. In particular: keys sent between KIF components satisfy Control Objective 3; distributed KIF functions (for example a host that generates keys and a host that distributes them) use mutually authenticated channels; loading enciphered keys into POI devices satisfies Control Objective 4; setting up the mutually authenticated channel satisfies Control Objective 4; a mutually authenticated channel carries the establishment of enciphered keys linking POI devices with the KIF's HSM; the sending and receiving devices authenticate one another, the KIF checking a POI's credentials before any key transport, exchange or establishment and the POI checking the KDH's, and where a KLD sits between the POIs and the KIF HSM, no unauthorised SCD can be slipped into the flow without detection; controls stop an unauthorised host from injecting keys into POIs and stop an unauthorised POI from setting up a key with a genuine KIF component.

Maintained by Gerard BlokdykControl text last updated

Other controls in Domain 5: P2PE Cryptographic Key Operations and Device Management – 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.