Configuration identification and change control generate the status accounting documented information that makes the evolving configuration visible, traceable and efficiently managed; it usually records the configuration information (identification number, title, dates of effect, revision status, history of changes, which baselines it belongs to), the configuration of the product or service (part numbers, design or build status), whether new configuration information has been released, and how changes have been processed. This information should be retained as it evolves, with the cross-references and relationships the reports require, and configuration items and their information should be kept in an environment suited to their condition, safeguarded against unauthorised change and loss of integrity, covered by disaster recovery, ready and fit for use wherever and whenever it is needed, and retrievable.
This control maps to 29 controls across 21 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 29 it maps to, and the evidence behind each claim, over MCP and REST.