PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.3.3: 12.3.3 Cryptographic cipher suite and protocol inventory reviewed annually

The cipher suites and protocols in use must be documented, then checked at least every 12 months, with the review covering at minimum: a current inventory of every cipher suite and protocol in use, stating its purpose and where it is used; active tracking of industry developments on whether each remains viable; and a documented plan for responding to expected changes in cryptographic weaknesses. Applicability: covers every suite and protocol used to satisfy PCI DSS, including those rendering PAN unreadable at rest and in transit, protecting passwords, and supporting authentication. Objective under the customized approach: the entity can react fast to cryptographic protocol or algorithm weaknesses that affect cardholder data protection. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 45 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.

ISO 27001:2022 · 5 controls

  • 5.35 Independent review of information security
  • 5.9 Inventory of information and other associated assets
  • 8.24 Use of cryptography
  • 8.32 Change management
  • 8.8 Management of technical vulnerabilities

NIST SP 800-53 Rev 5 · 5 controls

SOC 2 · 5 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

CIS Controls v8 · 3 controls

  • CIS-12.6 Use of Secure Network Management and Communication Protocols
  • CIS-2.1 Establish and Maintain a Software Inventory
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

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

Azure Security Benchmark · 2 controls

  • ASBv3-DP-7 Use a secure certificate management process
  • DP-3 Encrypt sensitive data in transit

FedRAMP High · 2 controls

  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection

FedRAMP Moderate · 2 controls

  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection

ISO 27701:2019 · 2 controls

  • 6.7 Cryptography
  • 6.7.1 Cryptographic controls

AWS Well-Architected Security Pillar · 1 control

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

NIS2 Directive · 1 control

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

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P2-5.3.4 P2-5.3.4 TLS configurations monitored for change

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 12: Information Security Policies

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

PCI DSS 4.0 12.3.3 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 45 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls