For module and integration testing the table lists probabilistic testing, dynamic analysis and testing, data recording and analysis, functional and black-box testing (HR at every SIL), performance testing, model-based testing, interface testing, test management and automation tools, forward traceability from the software design spec to the module and integration tests (R at SIL 1 and 2, HR at SIL 3 and 4), and formal verification, which may reduce the testing needed.
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.