Configuration management lets the item be replicated consistently, its information regenerated and modifications controlled. Objectives: each configuration item has a unique identity and documentation; consistent, accurate replication is ensured; and modifications are identified and tracked in a controlled way. Activities cover unique identification and control of items (hardware, design representations, tools and other data used for credit, baselines), baselines, problem reporting, change control with traceability of changes (life cycle data secure and retrievable), and controlled archiving, retrieval and release.
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.