Class II hardware elements (more complex components such as ADCs and sensors) are evaluated by a hardware element evaluation plan, tests and analysis of the failure modes, failure rates and diagnostic capability relevant to the safety requirements, with an evaluation report. This sits in clause 13, whose stated aim is adequate functional behaviour of COTS or custom hardware elements not developed under the standard, so the risk from their systematic faults is low enough, as an alternative means of compliance with part 5, with suitability for random faults left to the integrator. 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.