Every lifecycle phase (overall, E/E/PE or software) gets a verification plan, set up alongside the development work for that phase, documenting or referencing which criteria, techniques and tools apply. Verification is performed to that plan, and information on it is gathered and recorded as proof that the phase was completed satisfactorily in every respect. The objective (7.18.1) is to show by review, analysis and/or test that each phase's outputs meet all of its objectives and requirements; the choice of techniques and the independence of verifiers depend on factors such as novelty of design and technology and may be set by sector standards.
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.