PCI DSS 4.0
Req 3: Protect Stored Account Data

PCI DSS 4.0 3.7.2: 3.7.2 Secure distribution of cryptographic keys

Key-management policies and procedures must be in place covering the secure distribution of keys that protect stored account data. Guidance clarifies that secret or private keys should reach only authorized custodians (as identified in 3.6.1.2) and never be sent by insecure means. Customized approach objective: keys stay protected while being distributed.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 19 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

SOC 2 · 4 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • SC-12 Cryptographic Key Establishment and Management

FedRAMP Moderate · 1 control

  • SC-12 Cryptographic Key Establishment and Management

ISO 27001:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27002:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls
  • 03.13.10 Cryptographic Key Establishment and Management
  • NIST800-SC-12 SC-12 Cryptographic Key Establishment and Management
  • P2-6.1.5 P2-6.1.5 Keys managed securely through their whole lifecycle

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 Req 3: Protect Stored Account Data

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 3.7.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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