Every stakeholder, system and system element requirement possesses nine characteristics: necessary (an essential capability, characteristic, constraint or quality factor whose omission leaves a gap nothing else fills, still current, with any planned expiry or applicability date marked); appropriate (detail and intent suit the level of the entity, leaving architecture and design free where possible, with extra detail held in attributes such as rationale); unambiguous (one interpretation only, simply stated); complete (understood without further information); singular (one capability, characteristic, constraint or quality factor, although several conditions may apply); feasible (achievable within cost, schedule and technical limits at acceptable risk); verifiable (its realization can be proven to the customer at the level where it sits, helped by being measurable); correct (a faithful expression of the need it came from); and conforming (follows the approved template and style where one applies).
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.