The symptoms of an incident are identified and logged, likely causes worked out and the incident allocated for resolution: the relevant symptoms are described so that probable causes can be found by consulting knowledge sources, known errors and problem records among them, and possible workarounds are identified; where there is no matching problem or known error and the incident meets the criteria for problem registration, a new problem is opened; and incidents that call for deeper expertise are passed to specialist functions, involving management at the right level.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.