The hardware architectural design implements the hardware safety requirements, each hardware component inheriting the highest ASIL of the requirements it implements, with the non-functional causes of failure (temperature, vibration, water, dust, EMI, crosstalk) considered and modularity, granularity and simplicity favoured. Sub-clause title from the held contents page; the clause's objectives quoted by a certification body; requirement text not held.
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.