The incidents that concern IRBC sit at the highest level of the organization's incident classification: judged very unlikely, but with a significant or catastrophic effect on ICT services if they happen. The aim of IRBC is strategies that help the organization prevent, respond to and recover from incidents affecting ICT services. What sets off the IRBC plans should be specified within the incident management process, including the information security incident response plans, which can provide for three interactions as events and incidents unfold: a link between the incident coordinator (ISO/IEC 27035-1) and whoever is responsible for IRBC, made as soon as a possible effect on business continuity is recognised; communication channels and procedures prepared in advance for handing operational responsibility from incident management to the IRBC response, so that no time is lost uncontrolled and agreed deadlines are met; and a planned handback of responsibility from IRBC to the incident coordinator, so that the incident report can be prepared and improvement proposals raised as lessons learned (ISO/IEC 27035-1:2023, Clause 5). New technical content in the second edition.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.