The organization shall establish, execute and maintain processes ensuring that identified safety anomalies are explicitly communicated to the persons responsible in the safety lifecycle, and a safety anomaly resolution process ensuring they are analysed, evaluated, resolved and managed in a timely and effective manner; a safety anomaly shall only be considered closed when the closure conditions are met (a rationale for closing it shall be recorded and reviewed), and unresolved anomalies shall be escalated to the persons responsible for functional safety, for example those in product development for anomalies found in development or in production and service for those found in the field.
This control maps to 1 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 1 it maps to, and the evidence behind each claim, over MCP and REST.