Where POS POI terminals at a merchant or payment acceptance site still use SSL or early TLS, the entity must verify that no known exploit of those protocols works against the devices. Applicability: aimed at the entity owning the terminal, such as a merchant, not at service providers acting as termination or connection points (those providers are covered by A2.1.3 and A2.1.2). The allowance rests on currently known risks; if a new exploit affects the terminals, they will need to be updated immediately. Guidance: moving to a secure protocol at the earliest opportunity is strongly recommended, and where the environment does not need SSL/early TLS, its use and fallback should be disabled. Objective under the customized approach: not eligible for the customized approach.
PCI DSS 4.0 A2.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.
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.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.