The entity adopts internal rules for changing critical information assets, meaning its systems, supporting infrastructure, processes, activities, configurations, software and firmware, so that changes do not cause incidents. Before a change the entity runs a risk analysis and assessment under Article 7. Each change is planned with deadlines and responsibilities for the steps before, during and after; coordinated in advance with everyone responsible for in-scope processes; approved by the head of the entity or an authorised person; communicated to interested parties at least three days before it is made; and tested in a test environment. A rollback plan to return systems to their prior state is prepared so that an incident caused by the change is short-lived.
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.