Physical stores of data are identified, linked to the logical business functions and data domains they serve, and defined and modelled with standard classifications and identifiers, so the organization knows where each kind of data resides. Carries forward v2.2 capabilities 3.3 (identifying the data, with needed data identified in logical terms and its physical sources documented) and 3.4 (define the data, structurally and semantically).
This control maps to 3 controls across 2 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 3 it maps to, and the evidence behind each claim, over MCP and REST.