Lasting solutions that remove the root cause are found and launched, with change requests passed to change management where needed, and the people affected are told what has been done and how recurrence will be prevented: a problem record is closed once it is confirmed that the known error has been removed, or once the business has agreed to deal with it some other way; the service desk learns when closure is expected (the fix date, the workaround, or that the problem stays open until the change goes in); change management reports regularly on how resolution of problems and errors is progressing; the ongoing effect of open problems and known errors on services is watched; the outcome of fixes to major problems is reviewed and confirmed; and what that review teaches is taken into a service review held with the business customer.
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.