3.6: 1. Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse that include: (a) Access to keys is restricted to the fewest number of custodians necessary, (b) Key-encrypting keys are at least as strong as the data-encrypting keys they protect, (c) Key-encrypting keys are stored separately from data-encrypting keys, (d) Keys are stored securely in the fewest possible locations and forms.
  • Examine documented key-management policies and procedures to verify that processes to protect cryptographic keys used to protect stored account data against disclosure and misuse are defined to include all elements specified in this requirement.

Description

Purpose

Cryptographic keys must be strongly protected because those who obtain access will be able to decrypt data.

Good Practice

Having a centralized key management system based on industry standards is recommended for managing cryptographic keys.

Further Information

The entity’s key management procedures will benefit through alignment with industry requirements, Sources for information on cryptographic key management life cycles include:

• ISO 11568-1 Banking — Key management (retail) — Part 1 : Principles (specifically Chapter 10 and the referenced Parts 2 and 4)

• NIST SP 800-57 Part 1 Revision 5— Recommendation for Key Management, Part 1: General .

3.6: 1.1. Additional requirement for service providers only: A documented description of the cryptographic architecture is maintained that includes: (a) Details of all algorithms, protocols, and keys used for the protection of stored account data, including key strength and expiry date, (b) Preventing the use of the same cryptographic keys in production and test environments. This bullet is a best practice until its effective date; refer to Applicability Notes below for details, (c) Description of the key usage for each key, (d) Inventory of any hardware security modules (HSMs), key management systems (KMS), and other secure cryptographic devices (SCDs) used for key management, including type and location of devices, to support meeting Requirement 12.3.4.
  • Additional testing procedure for service provider assessments only: Interview responsible personnel and examine documentation to verify that a document exists to describe the cryptographic architecture that includes all elements specified in this requirement.

Description

Purpose

Maintaining current documentation of the cryptographic architecture enables an entity to understand the algorithms, protocols, and cryptographic keys used to protect stored account data, as well as the devices that generate, use, and protect the keys. This allows an entity to keep pace with evolving threats to its architecture and plan for updates as the assurance level provided by different algorithms and key strengths changes. Maintaining such documentation also allows an entity to detect lost or missing keys or key- management devices and identify unauthorized additions to its cryptographic architecture.

The use of the same cryptographic keys in both production and test environments introduces a risk of exposing the key if the test environment is not at the same security level as the production environment.

Good Practice

Having an automated reporting mechanism can assist with maintenance of the cryptographic attributes.

3.6: 1.2. Secret and private keys used to protect stored account data are stored in one (or more) of the following forms at all times: (a) Encrypted with a key-encrypting key that is at least as strong as the data-encrypting key, and that is stored separately from the data- encrypting key, (b) Within a secure cryptographic device (SCD), such as a hardware security module (HSM) or PTS-approved point-of-interaction device, (c) As at least two full-length key components or key shares, in accordance with an industry- accepted method.
  • Examine documented procedures to verify it is defined that cryptographic keys used to encrypt/decrypt stored account data must exist only in one (or more) of the forms specified in this requirement.
  • Examine system configurations and key storage locations to verify that cryptographic keys used to encrypt/decrypt stored account data exist in one (or more) of the forms specified in this requirement.
  • Wherever key-encrypting keys are used, examine system configurations and key storage locations to verify:
  • • Key-encrypting keys are at least as strong as the data-encrypting keys they protect.
  • • Key-encrypting keys are stored separately from data-encrypting keys.

Description

Purpose

Storing cryptographic keys securely prevents unauthorized or unnecessary access that could result in the exposure of stored account data. Storing keys separately means they are stored such that if the location of one key is compromised, the second key is not also compromised.

Good Practice

Where data-encrypting keys are stored in an HSM, the HSM interaction channel should be protected to prevent interception of encryption or decryption operations.

3.6: 1.3. Access to cleartext cryptographic key components is restricted to the fewest number of custodians necessary.
  • Examine user access lists to verify that access to cleartext cryptographic key components is restricted to the fewest number of custodians necessary.

Description

Purpose

Restricting the number of people who have access to cleartext cryptographic key components reduces the risk of stored account data being retrieved or rendered visible by unauthorized parties.

Good Practice

Only personnel with defined key custodian responsibilities (creating, altering, rotating, distributing, or otherwise maintaining encryption keys) should be granted access to key components.

Ideally this will be a very small number of people.

3.6: 1.4. Cryptographic keys are stored in the fewest possible locations.
  • Examine key storage locations and observe processes to verify that keys are stored in the fewest possible locations.

Description

Purpose

Storing any cryptographic keys in the fewest locations helps an organization track and monitor all key locations and minimizes the potential for keys to be exposed to unauthorized parties.