PCI DSS requirement 12.3.3: an inventory of your cipher suites and protocols
By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 2 min read · PCI DSS
The next SHA-1 or TLS 1.0 will not arrive on your schedule. Requirement 12.3.3 is about being able to answer quickly.
What 12.3.3 asks
- An up-to-date inventory of all cryptographic cipher suites and protocols in use, including their purpose and where they are used.
- Active monitoring of industry trends on the continued viability of each.
- A documented plan to respond to anticipated changes in cryptographic vulnerabilities.
- A review of all three at least once every 12 months.
Where cryptography hides
- Public TLS endpoints and the load balancers or CDNs that terminate them.
- Internal service-to-service traffic, including mutual TLS inside a service mesh.
- Database connections and replication links.
- VPN and remote administration: IPsec, SSH, bastion hosts.
- File transfers to processors and acquirers: SFTP, PGP-encrypted batches.
- Stored-data encryption and keyed hashes of PAN under 3.5.1 — strictly algorithms rather than cipher suites, but worth recording in the same place.
Building the inventory
Start from observation rather than documentation. Tools such as testssl.sh, sslyze or nmap's ssl-enum-ciphers script will tell you which protocol versions and suites an endpoint actually accepts. For cloud load balancers, record the named TLS security policy attached to each listener. For internal services, read the effective configuration and spot-check it with the same scanners from inside the network.
For each entry, record the system, its purpose, the protocol versions, the cipher suites, the certificate key type and size, and an owner. The owner matters most, because that is who acts when something on the list is deprecated.
Monitoring viability
Useful sources are NIST SP 800-52 for TLS configuration, vendor and browser deprecation notices, and PCI SSC guidance on strong cryptography. The forward-looking item for most inventories is post-quantum migration. NIST published its first post-quantum standards, including ML-KEM, in August 2024, and major browsers already negotiate hybrid key exchange. Your plan does not need to migrate everything now, but it should say which systems will need to and roughly when.
What a response plan looks like
- The trigger: a deprecation notice, a published attack, a standards change.
- How you find affected systems — which is what the inventory is for.
- Target timeframes by severity.
- Compatibility testing for clients and partners who may still depend on the old configuration.
- Communication to customers if their integrations are affected.