← PCI DSS 4.0.1 · Req 3 — Protect stored account data

3.6-3.7 — Cryptographic key management

high key-management

Requirement

Cryptographic keys used to protect stored account data are managed securely: access is restricted to the fewest custodians, keys are stored securely, key-management procedures cover generation, distribution, storage, cryptoperiod-based rotation, retirement and split knowledge/dual control where applicable, and custodians formally acknowledge their responsibilities.

What the engine looks for

Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.

Required element 1 — any one of
key managementencryption keyscryptographic keyskmshsmkey custodiankey custodianskey rotation
Required element 2 — any one of
rotat…custodiancustodianscryptoperiodrestrictedsplit knowledgedual controldocumentedprocedureprocedures
Supporting terms — specificity signals
3.6.13.7.13.7.4key-encrypting keyacknowledge
Contradiction markers

Finding any of these outranks coverage — a policy that admits the gap is worse than silence.

keys are stored in the source code keys in source control encryption keys are hardcoded

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

FrameworkControlTitleShared topics
HIPAA 164.312(a)(2)(iv) Encryption and decryption at rest (A) key-management
NIST CSF 2.0 PR.DS-01 Confidentiality, integrity and availability of data at rest key-management
ISO 27001 A.8.24 Use of cryptography key-management