Incident and change records, together with other operational data, are gathered and analysed so that trends pointing to emerging problems are spotted, and a problem record is opened for assessment: information on problems tied to incidents and changes is captured and shared with stakeholders, both in reports and in periodic joint sessions of the incident, problem, change and configuration management disciplines; the owners and managers of those processes hold regular sessions on open known problems and upcoming changes; lasting fixes that remove the root cause are launched through change requests; the change work triggered by problem management is recorded and reported so that the overall cost of problems can be tracked; reporting follows resolution progress against business needs and service level agreements, escalating where appropriate; and trends in problems are followed to make better use of resources and cut down on workarounds.
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.