Components are procured as the acquisition plan sets out, meeting the requirements and detailed designs, the principles and standards of the architecture, and the procurement and contracting procedures, quality requirements and approval processes the enterprise uses: the plan for acquiring components allows for later flexibility such as added capacity, and for transition costs, risk and upgrades across the life of the project; acquisition plans are reviewed and approved for risk, cost and benefit and for technical fit with architecture standards; how far an acquired solution will require business processes to change before its benefits are realised is assessed and recorded; the required approvals are obtained at key decision points; and every infrastructure and software acquisition received is entered in an asset inventory.
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.