Service providers only (an additional requirement). If customer user access relies on a password or passphrase alone (that is, any single-factor implementation), one of these must hold: the password or passphrase is replaced no less often than every 90 days; or account security posture is assessed dynamically and access decisions are made automatically in real time from it. Applicability: applies only when the assessed entity is a service provider; excludes consumers who log in to view their own payment card details. Until it took effect on 31 March 2025, service providers could satisfy either one of the two requirements (8.3.10 or this one). Objective under the customized approach: passwords and passphrases held by a service provider's customers cannot remain in use indefinitely. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 8 controls across 6 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.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 8 it maps to, and the evidence behind each claim, over MCP and REST.