Generate keys so they start in a pre-activated state, meaning that a new key cannot be used until someone has explicitly authorised its use. The process includes provisions for legal and regulatory requirements.
This control maps to 9 controls across 8 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.
Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CEK-15 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 9 it maps to, and the evidence behind each claim, over MCP and REST.