Service providers only (an additional requirement). If customers' users rely on passwords or passphrases alone as the authentication factor reaching cardholder data (any single-factor implementation), the service provider must give customer users guidance that includes: advice for customers to change their passwords or passphrases periodically; and advice on when, and in what circumstances, passwords or passphrases should be changed. Applicability: applies only when the assessed entity is a service provider; excludes consumers who log in to view their own payment card details. This requirement is superseded by 8.3.10.1 once that requirement takes effect. Objective under the customized approach: passwords and passphrases held by a service provider's customers cannot remain in use indefinitely.
This control maps to 14 controls across 10 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
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.
PCI DSS 4.0 8.3.10 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 14 it maps to, and the evidence behind each claim, over MCP and REST.