Traceability of the verified system or software elements is maintained: the trace is the one place that accounts for each requirement, linking it back to where it came from and onward to the evidence that it has been met. Each requirement carries its verification method and results, showing how the element is checked against it, links to work products are added at each later life cycle stage, and every requirement keeps a unique identifier. Anomalies found in verification may lead to requirement changes in any technical process.
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.