The plan should be checked for adequacy and effectiveness and given formal approval by an authorized individual, or by a group drawn from the relevant functions. Under a contract it may go to the customer for review and acceptance, before or after award; after award it should be looked at again and, where appropriate, updated for any requirement changes since the pre-contract discussions, and where a project or contract proceeds in stages a plan may be expected for each stage before that stage begins.
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.