3.6.1.2 Permitted storage forms for secret and private keys

Secret and private keys that protect stored account data must at all times exist in one or more of these forms: (1) wrapped by a key-encrypting key whose strength equals or exceeds that of the data-encrypting key, held apart from it; (2) inside a secure cryptographic device (SCD), for example an HSM or a point-of-interaction device with PTS approval; (3) split into at least two full-length components or shares using a method the industry accepts. Applicability: public keys need not be held in these forms; keys held in a KMS that uses SCDs are acceptable; merely splitting a key into two halves does not comply, and any key component or share has to be generated either by an approved random number generator inside an SCD OR in line with ISO 19592 or an equivalent standard for secret key share generation. Objective under the customized approach: secret and private keys are kept in a secure form that stops unauthorized retrieval or access.

Source: PCI DSS v4.0.1, 3.6.1.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.