PCI DSS 4.0
Req 3: Protect Stored Account Data

PCI DSS 4.0 3.6.1: 3.6.1 Procedures protect keys against disclosure and misuse

The entity defines and carries out procedures to shield the keys securing stored account data against misuse and disclosure, covering: (1) key access limited to the smallest number of custodians needed; (2) no key-encrypting key is weaker than any data-encrypting key it wraps; (3) key-encrypting keys kept apart from data-encrypting keys; and (4) keys held securely in as few locations and forms as possible. Applicability: covers keys protecting stored account data and key-encrypting keys that protect data-encrypting keys; both kinds need protection, and key-encrypting keys need especially strong measures because one may unlock many data-encrypting keys. Guidance recommends a centralized, standards-based key management system. Objective under the customized approach: processes guarding stored-data keys against misuse and disclosure are defined and running.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 6 controls

CMMC 2.0 · 4 controls

FedRAMP High · 4 controls

  • CP-9(8) System Backup | Cryptographic Protection (CP-9(8))
  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection
  • SC-28 Protection of Information at Rest

FedRAMP Moderate · 4 controls

  • CP-9(8) System Backup | Cryptographic Protection (CP-9(8))
  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection
  • SC-28 Protection of Information at Rest

ISO 27001:2022 · 4 controls

  • 5.15 Access control
  • 5.18 Access rights
  • 8.2 Privileged access rights
  • 8.24 Use of cryptography

ISO 27002:2022 · 4 controls

  • 5.15 Access control
  • 5.18 Access rights
  • 8.2 Privileged access rights
  • 8.24 Use of cryptography

Azure Security Benchmark · 2 controls

  • ASBv3-DP-6 Use a secure key management process
  • ASBv3-DP-8 Ensure security of key and certificate repository

ISO 27701:2019 · 2 controls

  • 6.7 Cryptography
  • 6.7.1 Cryptographic controls

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

PCI 3DS Core Security Standard · 2 controls

  • P2-6.1.1 P2-6.1.1 Cryptography and key-management policies and procedures
  • P2-6.1.7 P2-6.1.7 Keys used only for their intended purpose

AWS Well-Architected Security Pillar · 1 control

C5 (Germany) · 1 control

CIS Controls v8 · 1 control

  • CIS-16.11 Leverage Vetted Modules or Services for Application Security Components

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

  • CCM-CEK-01 Encryption and Key Management Policy and Procedures

HIPAA Security Rule · 1 control

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

  • 03.13.10 Cryptographic Key Establishment and Management

NIST SP 800-66 Rev 2 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

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.6.1 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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls