The activities are: planning the tools, methods, roles and responsibilities; configuration identification of design and development assurance items with the control category for each; establishing baselines and the control process for changing them, keeping each change traceable to the previous baseline; problem reporting and change control, in which each change record assesses the effect on requirements, on interfaces, on the safety analyses and on the V&V data, track changes to completion and share supplier problem reports and changes with the aircraft or system developer for higher-level effect evaluation; archive and retrieval of configuration items; and controlling new and modified requirements according to the plan.
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.