If a nonconformity arises, the organization must respond by acting to contain and correct it and by handling what follows from it; judge whether action is required to remove its causes, so that it neither comes back nor appears elsewhere, by examining it, finding its causes and checking whether similar nonconformities exist or might arise; carry out the action required; check that the corrective action worked; and change the system where needed. Corrective action must be proportionate to the effects of the nonconformity. Documented information must show what the nonconformities were and what was done, what the corrective action achieved, how security-related failures were investigated (near misses and false alarms included, as well as incidents, emergencies and nonconformities), and how their consequences were mitigated. Procedures must require any proposed corrective action to pass through the security-related risk assessment before it is put in place, except where acting at once prevents an imminent threat to life or public safety; and corrective action must be in proportion to how large the problem is and to the security-related risks it is likely to meet.
This control maps to 3 controls across 3 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 3 it maps to, and the evidence behind each claim, over MCP and REST.