Table A.7 lists the overall software testing techniques: performance testing (Table A.18) HR at SIL 1 and 2 and M at SIL 3 and 4; functional (black-box) testing (per Table A.14) HR at Basic Integrity to SIL 2 and M at SIL 3 and 4; modelling (Table A.17) R above Basic Integrity. At SIL 1 and 2 an approved combination is performance testing with functional testing. The Annex A note records that mandatory performance testing at SIL 3 and 4 may use a technique not listed in Table A.18 if the rationale is given, and that functional testing at Basic Integrity leaves the user free to choose among the Table A.14 techniques.
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.