For software verification the table lists formal proof, animation of specification and design, static analysis and dynamic analysis and testing (both HR from SIL 2), forward traceability from the software design spec to the verification plan (data verification included), backward traceability from that plan to the design spec (both R at SIL 1 and 2, HR at SIL 3 and 4), and offline numerical analysis; module, integration and validation testing are covered by Tables A.5 to A.7. Early phases are verified statically; once code exists dynamic testing adds evidence, and both kinds together give assurance.
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.