PCI DSS 4.0 3.6.1.1: 3.6.1.1 Service provider cryptographic architecture documented

Service providers only (an additional requirement): a written description of the cryptographic architecture is kept current and covers: (1) details of every algorithm, protocol and key used to protect stored account data, with key strength and expiry date; (2) prevention of the same cryptographic keys being used in both production and test environments; (3) how each key is used; and (4) an inventory of the HSMs, the key management systems (KMS) and any other secure cryptographic devices (SCDs) supporting key management, with device type and location, to support Requirement 12.3.4. Applicability: applies only when the assessed entity is a service provider; with cloud HSMs, responsibility for the architecture is split between cloud provider and cloud customer. Objective under the customized approach: correct, current information about the cryptographic architecture is maintained and can be produced. Future-dated (bullet on preventing the same keys being used in production and test): treated as a best practice up to 31 March 2025 and mandatory since then.

Maintained by Gerard BlokdykControl text last updated 21 May 2026

What else in your programme already covers this

This control maps to 22 controls across 14 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 · 4 controls

NIST800-PL-8 PL-8 Security and Privacy Architectures
NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design
NIST800-SC-12 SC-12 Cryptographic Key Establishment and Management
NIST800-SC-13 SC-13 Cryptographic Protection

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-CEK-01 Encryption and Key Management Policy and Procedures
CCM-CEK-21 Key Inventory Management

FedRAMP High · 2 controls

PL-8 Security and Privacy Architectures
SC-12 Cryptographic Key Establishment and Management

FedRAMP Moderate · 2 controls

PL-8 Security and Privacy Architectures
SC-12 Cryptographic Key Establishment and Management

ISO 27001:2022 · 2 controls

8.24 Use of cryptography
8.27 Secure system architecture and engineering principles

SOC 2 · 2 controls

SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
SOC2-CC6.1 CC6.1 Logical access security over protected information assets

AWS Well-Architected Security Pillar · 1 control

SEC08-BP01 Implement secure key management

Azure Security Benchmark · 1 control

ASBv3-DP-6 Use a secure key management process

C5 (Germany) · 1 control

C5-CRY-01 Policy for the use of encryption procedures and key management

ISO 27002:2022 · 1 control

8.24 Use of cryptography

ISO 27701:2019 · 1 control

6.7.1 Cryptographic controls

NIS2 Directive · 1 control

Art.21.2.h Policies and procedures on the use of cryptography and, where appropriate, encryption

NIST SP 800-171 Rev 3 · 1 control

03.13.10 Cryptographic Key Establishment and Management

PCI 3DS Core Security Standard · 1 control

P2-6.1.4 P2-6.1.4 Documented cryptographic architecture

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.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 gaps If you hold FedRAMP Moderate49.3% covered · 142 gaps If you hold NIST SP 800-53 Rev 547.5% covered · 147 gaps If you hold ISO 27002:202243.2% covered · 159 gaps If you hold CIS Controls v838.2% covered · 173 gaps If 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 each Browse the graph free

Query this from an agent

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

MCP endpoint All PCI DSS 4.0 controls