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