The Tester writes an Application Test Specification defining tests at intermediate or final stages of data preparation that confirm the data are coherent and complete against the application principles and against the specific application architecture; the Verifier checks that specification's readability, traceability, specific content and consistency. The Tester's Application Test Report records that those tests were run correctly and completely. Where Table A.1 requires, the Application Data Verification Report records every activity performed to establish the data's correctness, completeness and coherence with the application principles and architecture, and evaluates the data's compatibility with the conditions of the generic application.
This control maps to 3 controls across 2 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 3 it maps to, and the evidence behind each claim, over MCP and REST.