The project decides which system elements and information items become configuration items and gives them identifiers and attributes; the operational concept and the requirements at every level (stakeholder, system, software, element) are named as configuration-controlled information items in the configuration management planning and carry unique identifiers. Baselines are defined through the life cycle, commonly the functional (requirements) baseline of the agreed system requirements and external interfaces, the allocated baseline of the reviewed element specifications including interfaces, the developmental baseline of evolving configurations under supplier change authority, and the product baseline of the detailed specifications and design representing the completed system, each with the change authority recorded in the configuration management 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.