Feedback from the stakeholders affected is coordinated, and at agreed key stages the business sponsor or product owner approves and signs off the functional and technical requirements, the feasibility studies, the risk analyses and the solutions recommended: it is the sponsor or product owner who, guided by the business case, finally chooses the solution, the way it will be acquired and its high-level design, with approvals obtained from affected functions such as legal, IT and architecture; and quality reviews are held during and on completion of every key stage, iteration or release, judged against the acceptance criteria first agreed and signed off by sponsors and stakeholders.
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.