Verification data include the verification plan (roles and responsibilities, independence between design and verification, method definitions and assignment guidance, outputs and artefacts, key activities and their sequence, schedule, and criteria for credit from hardware and software verification), verification procedures and results, the verification matrix tracing each requirement to its verification method, procedures and results with its conclusion, and the verification summary, which assesses deficiencies and their impact on safety, including deferred problem reports; the summary also includes the data from investigating unintended behaviors (4.6.4).
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.