The enterprise understands the business's present issues, objectives and expectations of I&T, and it understands, manages and communicates requirements, with their status agreed and approved. Business stakeholders are identified together with their interests and responsibilities. The enterprise's direction, issues and strategic objectives, and how they fit the architecture, are reviewed. The business environment, constraints on processes, growth or shrinkage, and industry and regulatory drivers are understood. Business processes and the demand patterns that drive service volumes are kept in sight. Expectations are managed so that business units grasp priorities, dependencies and financial limits, and why their requests have to be scheduled. What the business expects of services and solutions enabled by I&T is clarified with acceptance criteria and metrics, and IT and every business department confirm that they agree on those expectations and on how they will be measured.
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.