The accepted solution is handed over to operations and the business, where appropriate first as a pilot or alongside the old solution for a set time, and any electronic or physical distribution is controlled so that it arrives intact and only at authorised locations: moving procedures, supporting services, applications and infrastructure out of testing into production follows the organisational change management and release management standards; how far pilot or parallel running goes is decided by the implementation plan; documentation of processes and systems, configuration information and contingency plans are brought up to date without delay; media libraries receive the transferred version straight away, and the previous version and its supporting configuration are archived; electronic distribution is controlled so that users are told and delivery goes only to authorised, correctly identified destinations, with confirmation that it has completed; and physical distribution is logged, recording what went out, to whom, where it was installed and when it was updated.
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.