A safety case that depends on the safety cases of subsystems, equipment or generic products references them in Part 5, demonstrates that every safety-related application condition each of them exports is either fulfilled within the dependent safety case or carried forward into its own application conditions, and keeps the dependency current: a change to a referenced safety case or its conditions is assessed for its effect on the dependent one, and the hierarchy of safety cases follows the system architecture.
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.