Conformance is claimed against the overall safety lifecycle of Figure 2; a different lifecycle may be used only if it is specified within the functional safety management activities and still meets every objective and requirement. Functional safety management runs in parallel with the lifecycle; every phase is applied unless justified; each phase is broken into elementary activities with defined scope, inputs and outputs; scope, inputs and outputs follow Table 1 unless justified under functional safety management or set by a sector standard; each phase's outputs must meet that phase's objectives and requirements (7.2 to 7.17); and each phase is verified under 7.18. The 7.1.3 objectives are to structure the phases systematically and to document key functional safety information across the lifecycle.
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.