PCI DSS 4.0
Appendix A2: Entities using SSL/early TLS for card-present POS POI terminal connections – PCI DSS 4.0

PCI DSS 4.0 A2.1.3: A2.1.3 Service providers offer a secure protocol option

Every service provider must provide a secure service offering. The testing procedure reads this as offering customers a secure protocol choice for the service. Guidance: customers need the option of upgrading and often migrate their POS POI estate gradually, so they need the provider to support a secure offering. Applicability: only when the assessed entity is a service provider. Objective under the customized approach: not eligible for the customized approach.

Maintained by Gerard BlokdykControl text last updated

Other controls in Appendix A2: Entities using SSL/early TLS for card-present POS POI terminal connections – PCI DSS 4.0

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

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

MCP endpointAll PCI DSS 4.0 controls