Each requirement's status, rejected requirements included, is followed across the project life cycle, and approval of changes to requirements is managed: every change request is assessed, categorised and prioritised for its effect on building the solution, on the original business case and on the budget; changes are tracked so that every stakeholder can monitor, review and approve them and the results are understood and agreed; and change requests are carried out without compromising the integrity of integration and configuration, while major upgrades to the solution are assessed and classified using agreed objective criteria.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.