Information passed from system development to hardware may include the design and safety requirements given to hardware; the assurance level of each function with its requirements and failure conditions; probability budgets and at-risk exposure times allocated to hardware functional failures; the hardware/software interface description; required safety strategies and design constraints (testability, design methods, architectures); system verification activities to be performed at hardware level; installation, ergonomic and environmental requirements; and integration problem reports that may affect requirements.
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.