Verification methods are defined with guidance for assigning one or more to each requirement, the prior edition's methods being inspection or review, analysis, modeling, test (including demonstration) and similarity or service experience, chosen more freely under Revision B; test procedures state their success criteria or expected results, give setup and steps sufficient for repeatability and reference the requirements they cover, and test results record the procedure version, the design configuration and setup and a pass or fail determination or the problem report raised, with tests also building confidence that the system does what is intended and nothing unintended.
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.