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.1.1 Summary of Protection and Assurance Requirements for Cryptographic 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.1

Title

Summary of Protection and Assurance Requirements for Cryptographic Keys

Control

Table 5 provides a summary of the protection requirements for keys during distribution and storage. Methods for providing the necessary protection are discussed in Section 6.2 . Guide to Table 5 : a. Column 1 (Key Type) identifies the key types. b. Column 2 (Security Service) indicates the type of security service that is provided by the key in conjunction with a cryptographic technique. In some cases, the word "support" is used in this column. This means that the associated key is used to support the primary cryptographic services of confidentiality, integrity authentication, and source authentication. For example, a key-agreement key may support a confidentiality service by establishing the key used to provide confidentiality; an RBG key supports the use of cryptography because it is used to provide the random values for generating the keys to be used to cryptographically protect information. c. Column 3 (Security Protection) indicates the type of protection required for the key (i.e., integrity and confidentiality). d. Column 4 (Association Protection) indicates the types of associations that need to be protected for that key, such as associating the key with the usage or application, the authorized communications participants or other indicated information. The association with domain parameters applies only to algorithms where they are used. e. Column 5 (Assurances Required) indicates whether assurance of public-key validity and/or assurance of private-key possession needs to be obtained as defined in [SP800- 56A] , [SP800-56B] , [SP800-89] and this Recommendation. Assurance of public-key validity provides a degree of confidence that a key is arithmetically correct. See Section 5.4.3 for further details. Assurance of private-key possession provides a degree of confidence that the entity providing a public key actually possessed the associated private key at some time. See Section 5.4.4 for further details. f. Column 6 (Period of Protection) indicates the length of time that the integrity and/or confidentiality of the key needs to be maintained (see Section 5.3 ). Symmetric keys and private keys shall be destroyed at the end of their period of protection (see Sections 8.3.4 and 9.3 ). Table 5: Protection requirements for cryptographic keys

Security Service Security Protection Association Protection Assurances Required Period of Protection Private signature key Source authentication Integrity authentication Support non- repudiation Integrity 30

Confidentiality Usage or application Domain parameters (when used) Public signature- verification key Possession From generation until the end of the cryptoperiod

Public signature- verification key Source authentication Integrity authentication Support non- repudiation Integrity Usage or application Key pair owner Domain parameters (when used) Private signature key Signed data Validity From generation until no protected data needs to be verified

Symmetric authentication key Source authentication Integrity authentication Integrity Confidentiality Usage or application Other authorized entities Authenticated data From generation until no protected data needs to be verified

Private authentication key Source authentication Integrity authentication Integrity Confidentiality Usage or application Public authentication key Domain parameters (when used) Possession From generation until the end of the cryptoperiod

Public authentication key Source authentication Integrity authentication Integrity Usage or application Key pair owner Authenticated data Private authentication key Domain parameters (when used) Validity From generation until no protected data needs to be authenticated

30 Integrity protection can be provided by a variety of means. See Sections 6.2.1.2 and 6.2.2.2 . Security Service Security Protection Association Protection Assurances Required Period of Protection Symmetric data- encryption/ decryption key Confidentiality Integrity Confidentiality Usage or application Other authorized entities Plaintext/Encrypted data From generation until the end of the lifetime of the data or the end of the cryptoperiod, whichever comes later Symmetric key-wrapping key Support Integrity Confidentiality Usage or application Other authorized entities Encrypted keys From generation until the end of the cryptoperiod or until no wrapped keys require protection, whichever is later. Symmetric RBG keys Support Integrity Confidentiality Usage or application From generation until replaced

Symmetric master key Support Integrity Confidentiality Usage or application Other authorized entities Derived keys From generation until the end of the cryptoperiod or the end of the lifetime of the derived keys, whichever is later. Private key- transport key Support Integrity Confidentiality Usage or application Encrypted keys Public key-transport key Possession From generation until the end of the period of protection for all transported keys Public key- transport key Support Integrity Usage or application Key pair owner Private key-transport key Validity From generation until the end of the cryptoperiod

Symmetric key-agreement key Support Integrity Confidentiality Usage or application Other authorized entities From generation until the end of the cryptoperiod or until no longer needed to determine a key, whichever is later Private static key-agreement key Support Integrity Confidentiality Usage or application Domain parameters (when used) Public static key- agreement key Possession From generation until the end of the cryptoperiod or until no longer needed to determine a key, whichever is later Security Service Security Protection Association Protection Assurances Required Period of Protection Public static key-agreement key Support Integrity Usage or application Key pair owner Domain parameters (when used) Private static key- agreement key Validity From generation until the end of the cryptoperiod or until no longer needed to determine a key, whichever is later

Private ephemeral key-agreement key Support Integrity Confidentiality Usage or application Public ephemeral key-agreement key Domain parameters (when used) From generation until the end of the key-agreement process After the end of the process, the key shall be destroyed Public ephemeral key-agreement key Support Integrity 31 Key pair owner Private ephemeral key-agreement key Usage or application Domain parameters (when used) Validity From generation until the key- agreement process is complete

Symmetric authorization keys Authorization Integrity Confidentiality Usage or application Other authorized entities From generation until the end of the cryptoperiod of the key Private authorization key Authorization Integrity Confidentiality Usage or application Public authorization key Domain parameters (when used) Possession From generation until the end of the cryptoperiod of the key

Public authorization key Authorization Integrity Usage or application Key pair owner Private authorization key Domain parameters (when used) Validity From generation until the end of the cryptoperiod of the key

31 The confidentiality of public ephemeral key-agreement keys may not be protected during transmission; however, the key-agreement protocols may be designed to detect unauthorized substitutions and modifications of the transmitted public ephemeral keys. In this case, the protocols form the data integrity mechanism.