Problems are investigated and diagnosed, drawing on the right subject matter experts to work out and analyse the root cause: candidate known errors are found by matching incident data against the store of known and suspected errors, including those reported by vendors, and are then classified as known errors; the configuration items affected are linked to the known error; and reporting shows how resolution is advancing and tracks the ongoing effect of problems still open, with the handling status of each problem followed from start to finish.
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.