Program change control procedures ensure only authorised program versions reach production: version control over source code and every software component; records of every installation or modification with date, reason or nature, the procedures to bring the component into service and the users involved; a rollback plan with complete backups of previous versions tested before production; an emergency change policy; testing and migration procedures; segregation of duties among developers, quality assurance, migration team and users; and updating of technical and user documentation after changes.
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.