Configuration management, both a development and a certification activity, ensures that configuration items (aircraft, system and item data and the development assurance data) are identified, that configuration baselines and their derivatives are established, that changes are controlled by reporting problems, controlling and reviewing changes and accounting for configuration status, and that configuration data can be archived and retrieved, with requirement and design changes implemented only through authorized change records.
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.