Control deficiencies are identified, their root causes analysed, and they are escalated and reported to stakeholders: process owners and I&T stakeholders are told the procedures for escalating exceptions, analysing root causes and reporting; thresholds for escalating exceptions and breakdowns are set according to the related enterprise risk; exceptions are identified, reported and logged, and someone is made responsible for resolving each and reporting its status; a decision is made on which exceptions go to the head of the responsible function and which are escalated, and affected owners and stakeholders are informed; every exception is followed up to confirm the agreed actions happened; and remedial actions that come out of control assessment and reporting are identified, started, tracked and carried through.
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.