Validation produces a matrix listing the requirements with their validation results, covering where relevant the performance of hardware and software, any derived requirements, aspects of environment and operation, requirements resting on assumptions and the supporting data; every requirement's origin can be identified, and the matrix is kept current during development and becomes part of the validation summary.
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.