Two control categories apply: HC1, with all CM activities, and HC2, a lighter set for data not expected to change incrementally but to be superseded. Per Table 7-1, both categories need configuration identification, baseline traceability, protection and identification under change control, retrieval, retention and protection against unauthorised change; HC1 alone needs baselines, problem reporting, change records, approvals and traceability, release, and media selection, refreshing and duplication. Appendix A sets the category of each data item by assurance level.
This control maps to 1 controls across 1 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 1 it maps to, and the evidence behind each claim, over MCP and REST.