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.3.2 Metadata for Related Cryptographic Information

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.3

Title changed

Before · SP 800-57 Part 1 Rev. 4

Metadata for Related Cryptographic Information

After · SP 800-57 Part 1 Rev. 5

Metadata for Related Cryptographic Information

Control changed

Before · SP 800-57 Part 1 Rev. 4

Cryptographic information other than keying material may need metadata to “point to” the keying material that was used to provide the cryptographic protection for the information. The metadata may also contain other related cryptographic information. When metadata is used, the metadata should accompany the information (i.e., the metadata is typically stored or transmitted with the information) and contain some subset of the following: 1. The type of information (e.g., domain parameters); 2. The source of the information (e.g., the entity that sent the information); 3. The application for using the key (e.g., purchasing or email); 4. Other associated cryptographic information (e.g., a key, MAC or hash value); and 5. Any other information (e.g., who has access rights).

After · SP 800-57 Part 1 Rev. 5

Cryptographic information other than keying material may need metadata to “point to” the keying material that was used to provide the cryptographic protection for the information. The metadata may also contain other related cryptographic information. When metadata is used, the metadata should accompany the information (i.e., the metadata is typically stored or transmitted with the information) and contain some subset of the following: 1. The type of information (e.g., domain parameters); 2. The source of the information (e.g., the entity that sent the information); 3. The application for using the key (e.g., purchasing or email); 4. Other associated cryptographic information (e.g., a key, MAC or hash value); and 5. Any other information (e.g., who has access rights).