Requirements are validated at every level of the hierarchy (aircraft, system, item), including the management of assumptions, with inputs that may include the system description and operating environment, system requirements, architecture and development assurance level. The validation plan defines the validation methods to be used, the data to be collected, data storage needs and the schedule (5.4.2.1); once the safety assessment has assigned function levels, the required validation approach is applied to that function's requirements (5.4.2.2).
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.