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.1 Metadata for Keys

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

Title

Metadata for Keys

Control

Metadata is used to provide information about the key, including its parameters, or the intended use of a key, and as such, contains the key’s control information. Different applications may require different metadata elements for the same key type, and different metadata elements may be required for different key types. It is the responsibility of an implementer to select suitable metadata elements for keys. When metadata is used, the metadata should accompany a key (i.e., the metadata is typically stored or transmitted with a key). Some examples of metadata elements are: 1. Key identifier; 2. Information identifying associated keys (e.g., the association between a public and private key); 3. Identity of the key’s owner or the sharing entity(ies); 4. Cryptoperiod (e.g., the start and end dates); 5. Key type (e.g., a signing private key, encryption key, or master key); 6. Application (e.g., purchasing or email); 7. Sensitivity of the information protected by the key;