Validation shows that the process in the work instruction meets the requirements agreed with the client, by evidence that it gives correct outputs for the defined inputs, without looking at how it is implemented; where possible it also establishes boundary conditions and error rates. It is usually done by black box testing so that implementation knowledge cannot steer the tests or results. The validation plan and its data are produced independently of design and implementation and rest only on the agreed requirements. Processes built on unverified tools or methods can still be validated if they give consistent results (compare the repeatability and reproducibility expectations of ISO/IEC 27037).
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.