BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

6.2.2.5 Association with the Other Entities

NIST platform security: roots of trust, firmware and secure enclaves SP 800-57 Part 1 Rev. 5 against SP 800-57 Part 1 Rev. 4
All changes in this version
removed 6 Training: If the new system requires that new or different tasks (e.g., key part of 6.2.2

Title changed

Before · SP 800-57 Part 1 Rev. 4

Association with the Other Entities

After · SP 800-57 Part 1 Rev. 5

Association with the Other Entities

Control changed

Before · SP 800-57 Part 1 Rev. 4

Some cryptographic information needs to be correctly associated with another entity (e.g., the key source), and the integrity of this association shall be maintained. For example, a symmetric (secret) key used for the encryption of information, or the computation of a MAC needs to be associated with the other entity(ies) that share(s) the key. Public keys need to be correctly associated (e.g., cryptographically bound) with the owner of the key pair (e.g., using public-key certificates). The cryptographic information shall retain its association during storage by separating the information by “entity” or application, or by using appropriate metadata for the information. Section 6.2.3 addresses the metadata used for cryptographic information.

After · SP 800-57 Part 1 Rev. 5

Some cryptographic information needs to be correctly associated with another entity (e.g., the key source), and the integrity of this association shall be maintained. For example, a symmetric (secret) key used for the encryption of information, or the computation of a MAC needs to be associated with the other entity(ies) that share(s) the key. Public keys need to be correctly associated (e.g., cryptographically bound) with the owner of the key pair (e.g., using public-key certificates). The cryptographic information shall retain its association during storage by separating the information by “entity” or application, or by using appropriate metadata for the information. Section 6.2.3 addresses the metadata used for cryptographic information.