Extends ISO/IEC 27002:2022 5.26. Each information security incident leads the processor, inside its incident management process, to check whether PII has been breached (then A.10.1 applies). An information security event, one that neither causes nor makes significantly likely unauthorised access to PII or to the equipment or premises storing it (for example broadcast attacks and pings against firewalls or edge servers, port scanning, failed log-ons, denial of service, packet sniffing), need not trigger that check. Carried from the 2019 guidance on the whole incident objective: incident handling and improvement can be shared roles across the cloud reference architecture, so the processor may need to work with the customer.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.