A cryptographic validation mechanism, such as hashes or key check values under ISO 11568, confirms that loaded keys and components are authentic and intact; check values are produced by a process that uses every part of the key or component, TDEA may use either the CMAC method or encryption of a zero block while AES must use CMAC, and the truncation rules apply wherever check values are recorded or displayed.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.