Verification, documented in the verification plan, should identify requirements needing verification (not necessarily at every level; a higher level may serve); select and perform methods (tests, simulation, prototyping, analyses, reviews); establish traceability between requirements, implementation, and verification procedures and results at a depth consistent with the assurance level (not down to resistors, capacitors or gates unless safety needs it); perform verification coverage analysis showing completeness, namely that each requirement is verified at some level by review, analysis or test, the method suits the requirement especially for safety, and results are correct with discrepancies explained or, without predefined expectations, consistent with the requirement; document results; and feed back omissions and errors.
This control maps to 5 controls across 3 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 5 it maps to, and the evidence behind each claim, over MCP and REST.