Planning underpins the whole process and coordinates configuration management work for a particular context across the life cycle. It produces the configuration management plan, which for a given product or service should be documented, approved and controlled, name the configuration management documented information that will be used, point to the organization's existing documented information wherever it can, and set out the resources, responsibilities, authorities and accountability for configuration management throughout the life cycle. The plan may stand alone, sit within another document or be split across several; a plan supplied by an external provider may be kept as it is or folded in. Annex A offers a structure and contents.
This control maps to 13 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.
The graph holds this control, the 13 it maps to, and the evidence behind each claim, over MCP and REST.