Individuals must not be able to submit a new password or passphrase that matches any of the last four they used. The guidance explains that keeping password history stops users cycling back to passwords that may have been guessed, brute-forced or changed due to suspected compromise. Applicability: not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction. Customized approach objective: an old password cannot be used again to reach an account for a minimum of 12 months.
This control maps to 15 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.7 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 15 it maps to, and the evidence behind each claim, over MCP and REST.