The enterprise defines and puts in place criteria and procedures for spotting and reporting problems, covering their classification, categorisation and prioritisation: problems are found by correlating incident reports, error logs and other inputs; every problem is handled through a formal route that can reach change, configuration, asset and incident data; support groups, selected on predefined characteristics, help to identify problems, analyse root causes and decide on solutions; priority levels are set with the business so that problem identification and root cause work happen in time under the SLAs, according to business impact and urgency; the service desk receives problem status so that customers and IT management stay informed; and one problem management catalogue records and reports problems and provides an audit trail of the process, status included.
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.