Business requirements for data, and their prioritization, are captured and aligned with business objectives, so that the scope of data the organization needs follows from its strategy and priorities rather than from technology projects. Elevated in v3 from part of the strategy to a capability of its own, with data requirements management among the concepts v3 adds; the data strategy then connects these prioritized requirements to the stakeholders who must agree them.
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.