Once configuration information has first been released, every change to it should be controlled, the level of control depending on what the change could lead to, on customer requirements and on the baseline. The documented change control process should cover a description of the change, its justification and documented information, its categorisation by complexity, resources and scheduling, then an evaluation of its consequences, how its disposition is decided, and how it is implemented and verified; concessions (also known as waivers or deviations) go through the same process.
This control maps to 10 controls across 5 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 10 it maps to, and the evidence behind each claim, over MCP and REST.