Key-management policies and procedures must be in place covering how keys that protect stored account data are stored securely. Guidance suggests wrapping data-encrypting keys with a key-encrypting key or holding keys in an HSM, and says secret or private keys able to decrypt data should never appear in source code. Guidance explains that keys stored without proper protection could let an attacker decrypt and expose account data. Customized approach objective: keys are protected while in storage.
This control maps to 22 controls across 15 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 3.7.3 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 22 it maps to, and the evidence behind each claim, over MCP and REST.