When planning the system, the organization considers the 4.1 issues and the 4.2 and 4.3 requirements and works out the risks and opportunities it must deal with to be confident the system will achieve its intended results, to prevent or reduce undesired effects and to keep improving. In doing so it takes account of hazards, risks, opportunities and its legal and other requirements. The processes and actions used to determine these risks and opportunities are kept as documented information to the degree needed for confidence that they run as planned.
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.