The organization must define and use a risk treatment process to choose suitable treatment options in light of the assessment results; determine every control needed to implement the chosen options (controls can be designed or taken from any source); compare those controls with Annex A to check nothing necessary has been left out (Annex A lists possible controls and is not exhaustive); produce a Statement of Applicability listing the necessary controls, why each is included, whether each is implemented, and why any Annex A control is excluded; draw up a risk treatment plan; and get risk owners to approve the plan and accept the residual risks. Documented information about the process must be retained. The process aligns with the principles and guidelines of ISO 31000.
This control maps to 4 controls across 3 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.
ISO 27001:2022 clause-6.1.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 4 it maps to, and the evidence behind each claim, over MCP and REST.