Passwords or passphrases belonging to any application or system account capable of interactive login must never be hard coded in scripts, in configuration or property files, or in bespoke or custom source code. The guidance suggests password vaults and other system-managed controls can help. Applicability: stored passwords must be encrypted in line with Requirement 8.3.2. Objective under the customized approach: unauthorized personnel are unable to use the passwords and passphrases of application and system accounts. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 34 controls across 18 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.6.2 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 34 it maps to, and the evidence behind each claim, over MCP and REST.