If user access relies on a password or passphrase alone (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, with access to resources decided automatically and in real time from that assessment. The guidance notes that dynamic analysis may weigh data points such as device integrity, location, access times and resources requested. Applicability: does not apply to in-scope components where MFA is used; not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction. Customer accounts of service providers are excluded, while accounts used by service provider staff are included. Objective under the customized approach: an undetected compromised password or passphrase cannot be used indefinitely.
This control maps to 19 controls across 12 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.9 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 19 it maps to, and the evidence behind each claim, over MCP and REST.