A safety case is built as the safety plan lays down, arguing that functional safety has been reached, and ought to gather the lifecycle's work products step by step as the evidence behind that argument; in distributed developments the item's safety case can combine the customer's and suppliers' safety cases with references to each party's evidence, and the intended safety argument can be defined before the work products exist to support the plan and the progressive functional safety assessment.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.