BaselineWatch
Desk

2 A compromise of the integrity of a key means that the key is incorrect − either that the key (was: Encrypt keys that can be decrypted using the corresponding)

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
modified 2 A compromise of the integrity of a key means that the key is incorrect − either that the key

Title changed

Before · SP 800-57 Part 1 Rev. 4

Encrypt keys that can be decrypted using the corresponding

After · SP 800-57 Part 1 Rev. 5

EncryptA keyscompromise of the integrity of a key means that canthe bekey decryptedis usingincorrect − either that the correspondingkey

Control changed

Before · SP 800-57 Part 1 Rev. 4

private key, or 3. Compute a shared secret during a key-agreement transaction.

Public-key certificate A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period.

Public-key (asymmetric) cryptographic algorithm A cryptographic algorithm that uses two related keys: a public key and a private key. The two keys have the property that determining the private key from the public key is computationally infeasible.

Public Key Infrastructure (PKI) A framework that is established to issue, maintain and revoke public- key certificates.

Random bit generator (RBG) A device or algorithm that outputs a sequence of bits that appears to be statistically independent and unbiased. Also, see Random number generator .

Random number generator (RNG) A process used to generate an unpredictable series of numbers. Also called a Random bit generator (RBG) .

Recipient-usage period The period of time during which the protected information is processed (e.g., decrypted).

Registration authority A trusted entity that establishes and vouches for the identity of a user.

Retention period The minimum amount of time that a key or other cryptographically related information should be retained in an archive.

RBG seed A string of bits that is used to initialize a DRBG. Also just called a Seed . Secret key A cryptographic key that is used with a secret-key (symmetric) cryptographic algorithm that is uniquely associated with one or more entities and is not made public. The use of the term “secret” in this context does not imply a classification level, but rather implies the need to protect the key from disclosure.

Secure communication protocol A communication protocol that provides the appropriate confidentiality, source authentication, and data integrity protection.

Security domain A system or subsystem that is under the authority of a single trusted authority. Security domains may be organized (e.g., hierarchically) to form larger domains.

Security life of data The time period during which the security of the data needs to be protected (e.g., its confidentiality, integrity or availability).

Security services Mechanisms used to provide confidentiality, integrity authentication, source authentication and/or support non-repudiation of information.

Security strength (Also “bits of security”) A number associated with the amount of work (that is, the number of operations) that is required to break a cryptographic algorithm or system. In this Recommendation, the security strength is specified in bits and is a specific value from the set {80, 112, 128, 192, 256}. Note that a security strength of 80 bits is no longer considered sufficiently secure.

Seed A secret value that is used to initialize a process (e.g., a DRBG). Also see RBG seed .

Self-signed certificate A public-key certificate whose digital signature may be verified by the public key contained within the certificate. The signature on a self- signed certificate protects the integrity of the data, but does not guarantee the authenticity of the information. The trust of self-signed certificates is based on the secure procedures used to distribute them.

Shall This term is used to indicate a requirement of a Federal Information Processing Standard (FIPS) or a requirement that must be fulfilled to claim conformance to this Recommendation. Note that shall may be coupled with not to become shall not .

Shared secret A secret value that has been computed using a key-agreement scheme and is used as input to a key-derivation function/method.

Should This term is used to indicate a very important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not .

Signature generation The use of a digital signature algorithm and a private key to generate a digital signature on data. Signature verification The use of a digital signature algorithm and a public key to verify a digital signature on data.

Source authentication The process of providing assurance about the source of information. Sometimes called identity authentication or origin authentication .

Split knowledge A process by which a cryptographic key is split into n key components, each of which provides no knowledge of the original key. The components can be subsequently combined to recreate the original cryptographic key. If knowledge of k (where k is less than or equal to n ) components is required to construct the original key, then knowledge of any k – 1 key components provides no information about the original key other than, possibly, its length. Note that in this Recommendation, split knowledge is not intended to cover key shares, such as those used in threshold or multi-party signatures.

Static key A key that is intended for use for a relatively long period of time and is typically intended for use in many instances of a cryptographic key- establishment scheme. Contrast with an Ephemeral key .

Symmetric key A single cryptographic key that is used with a secret (symmetric) key algorithm.

Symmetric-key algorithm A cryptographic algorithm that uses the same secret key for an operation and its complement (e.g., encryption and decryption).

System initialization A function in the lifecycle of keying material; setting up and configuring a system for secure operation.

Trust anchor 1. An authoritative entity for which trust is assumed. In a PKI, a trust anchor is a certification authority, which is represented by a certificate that is used to verify the signature on a certificate issued by that trust- anchor. The security of the validation process depends upon the authenticity and integrity of the trust anchor's certificate. Trust anchor certificates are often distributed as self-signed certificates. 2. The self-signed public key certificate of a trusted CA.

Unauthorized disclosure An event involving the exposure of information to entities not authorized access to the information.

User See Entity .

User initialization A function in the lifecycle of keying material; the process whereby a user initializes its cryptographic application (e.g., installing and initializing software and hardware). User registration A function in the lifecycle of keying material; a process whereby an entity becomes a member of a security domain.

X.509 certificate The X.509 public-key certificate or the X.509 attribute certificate, as defined by the ISO/ITU-T X.509 standard. Most commonly (including in this document), an X.509 certificate refers to the X.509 public-key certificate.

X.509 public-key certificate A digital certificate containing a public key for an entity and a name for that entity, together with some other information that is rendered un-forgeable by the digital signature of the certification authority that issued the certificate, encoded in the format defined in the ISO/ITU-T X.509 standard.

2.2 Acronyms The following abbreviations and acronyms are used in this Recommendation: 2TDEA Two-key Triple Data Encryption Algorithm specified in [SP800-67] . 3TDEA Three-key Triple Data Encryption Algorithm specified in [SP800-67] . AES Advanced Encryption Standard specified in [FIPS197] . ANS American National Standard. ANSI American National Standards Institute. CA Certification Authority. CRC Cyclic Redundancy Check. CRL Certificate Revocation List. DRBG Deterministic Random Bit Generator. DSA Digital Signature Algorithm specified in [FIPS186] . ECC Elliptic Curve Cryptography. ECDSA Elliptic Curve Digital Signature Algorithm specified in [ANSX9.62] and approved in [FIPS186] . FFC Finite Field Cryptography. FIPS Federal Information Processing Standard. HMAC Keyed-Hash Message Authentication Code specified in [FIPS198] . IFC Integer Factorization Cryptography. IV Initialization Vector. MAC Message Authentication Code. NIST National Institute of Standards and Technology. PKI Public-Key Infrastructure. POP Proof of Possession. RA Registration Authority. RBG Random Bit Generator. RNG Random Number Generator. RSA Rivest, Shamir, Adelman; an algorithm approved in [FIPS186] for digital signatures and in [SP800-56B] for key establishment. S/MIME Secure Multipurpose Internet Mail Extensions. TDEA Triple Data Encryption Algorithm; Triple DEA specified in [SP800-67] . TLS Transport Layer Security

After · SP 800-57 Part 1 Rev. 5

private key, or 3. Compute a shared secret during a key-agreement transaction.

Public-key certificate A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period.

Public-key (asymmetric) cryptographic algorithm A cryptographic algorithm that uses two related keys: a public key and a private key. The two keys have the property that determining the private key from the public key is computationally infeasible.

Public Key Infrastructure (PKI) A framework that is established to issue, maintain and revoke public- key certificates.

Random bit generator (RBG) A device or algorithm that outputs a sequence of bits that appears to be statistically independent and unbiased. Also, see Random number generator .

Random number generator (RNG) A process used to generate an unpredictable series of numbers. Also called a Random bit generator (RBG) .

Recipient-usage period The period of time during which the protected information is processed (e.g., decrypted).

Registration authority A trusted entity that establishes and vouches for the identity of a user.

Retention period The minimum amount of time that a key or other cryptographically related information should be retained in an archive.

RBG seed A string of bits that is used to initialize a DRBG. Also just called a Seed . Secret key A cryptographic key that is used with a secret-key (symmetric) cryptographic algorithm that is uniquely associated with one or more entities and is not made public. The use of the term “secret” in this context does not imply a classification level, but rather implies the need to protect the key from disclosure.

Secure communication protocol A communication protocol that provides the appropriate confidentiality, source authentication, and data integrity protection.

Security domain A system or subsystem that is under the authority of a single trusted authority. Security domains may be organized (e.g., hierarchically) to form larger domains.

Security life of data The time period during which the security of the data needs to
has bebeen protectedmodified (e.g., its confidentiality, integrity or availability).

Security services Mechanisms used to provide confidentiality, integrity authentication, source
either authenticationdeliberately and/or support non-repudiation of information.

Security strength (Also “bits of security”) A number associated with the amount of work (that is, the number of operations
accidentally) that is required to break a cryptographic algorithm or system. In this Recommendation, the security strength is specified in bits and is a specific value from the set {80, 112, 128, 192, 256}. Note that a security strength of 80 bits is no longer considered sufficiently secure.

Seed A secret value that is used to initialize a process (e.g., a DRBG). Also see RBG seed .

Self-signed certificate A public-key certificate whose digital signature may be verified by the public
another key contained within the certificate. The signature on a self- signed certificate protects the integrity of the data, but does not guarantee the authenticity of the information. The trust of self-signed certificates is based on the secure procedures used to distribute them.

Shall This term is used to indicate a requirement of a Federal Information Processing Standard (FIPS) or a requirement that must be fulfilled to claim conformance to this Recommendation. Note that shall may be coupled with not to become shall not .

Shared secret A secret value that
has been computed using a key-agreement scheme and is used as input to a key-derivation function/method.

Should This term is used to indicate a very important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not .

Signature generation The use of a digital signature algorithm and a private key to generate a digital signature on data. Signature verification The use of a digital signature algorithm and a public key to verify a digital signature on data.

Source authentication The process of providing assurance about the source of information. Sometimes called identity authentication or origin authentication .

Split knowledge A process
substituted; bythis whichincludes a cryptographic key is split into n key components, each of which provides no knowledge of the original key. The components can be subsequently combined to recreate the original cryptographic key. If knowledge of kdeletion (where k is less than or equal to n non-availability) components is required to construct the original key, then knowledge of any k – 1 key components provides no information about the original key other than, possibly, its length. Note that in this Recommendation, split knowledge is not intended to cover key shares, such as those used inThe thresholdsubstitution or multi-party signatures.

Static key A key that is intended for use for a relatively long period of time and is typically intended for use in many instances
modification of a cryptographic key- establishment scheme. Contrast with an Ephemeral key .

Symmetric key A single cryptographic key that is
used with a secret (symmetric) key algorithm.

Symmetric-key algorithm A cryptographic algorithm that uses the same secret key for an operation and its complement (e.g., encryption and decryption).

System initialization A function in the lifecycle of keying material; setting up and configuring a system for secure operation.

Trust anchor 1. An authoritative entity for which trust is assumed. In a PKI, a trust anchor is a certification authority, which is represented by a certificate that is used
to verify the signature on a certificate issued by that trust- anchor. The security of the validation process depends upon the authenticity andprovide integrity of the trust anchor's certificate. Trust anchor certificates are often distributed as self-signed certificates. 2. The self-signed public key certificate of a trusted CA.

Unauthorized disclosure An event involving the exposure of information to entities not authorized access to the information.

User See Entity .

User initialization A function in the lifecycle of keying material; the process whereby a user initializes its cryptographic application (e.g., installing and initializing software and hardware). User registration
66 Acalls functioninto inquestion the lifecycle of keying material; a process whereby an entity becomes a memberintegrity of a security domain.

X.509 certificate The X.509 public-key certificate or the X.509 attribute certificate, as defined by the ISO/ITU-T X.509 standard. Most commonly (including in this document), an X.509 certificate refers to the X.509 public-key certificate.

X.509 public-key certificate A digital certificate containing a public key for an entity and a name for that entity, together with some other
all information that is rendered un-forgeableprotected by the digital signature of the certification authority that issued the certificate, encoded in the format defined in the ISO/ITU-T X.509 standard.

2.2 Acronyms The following abbreviations and acronyms are used in this Recommendation: 2TDEA Two-key Triple Data Encryption Algorithm specified in [SP800-67] . 3TDEA Three-key Triple Data Encryption Algorithm specified in [SP800-67] . AES Advanced Encryption Standard specified in [FIPS197] . ANS American National Standard. ANSI American National Standards Institute. CA Certification Authority. CRC Cyclic Redundancy Check. CRL Certificate Revocation List. DRBG Deterministic Random Bit Generator. DSA Digital Signature Algorithm specified in [FIPS186] . ECC Elliptic Curve Cryptography. ECDSA Elliptic Curve Digital Signature Algorithm specified in [ANSX9.62] and approved in [FIPS186] . FFC Finite Field Cryptography. FIPS Federal Information Processing Standard. HMAC Keyed-Hash Message Authentication Code specified in [FIPS198] . IFC Integer Factorization Cryptography. IV Initialization Vector. MAC Message Authentication Code. NIST National Institute of Standards and Technology. PKI Public-Key Infrastructure. POP Proof of Possession. RA Registration Authority. RBG Random Bit Generator. RNG Random Number Generator. RSA Rivest, Shamir, Adelman; an algorithm approved in [FIPS186] for digital signatures and in [SP800-56B] for
key establishment. S/MIME Secure Multipurpose Internet Mail Extensions. TDEA Triple Data Encryption Algorithm; Triple DEA specified in [SP800-67] . TLS Transport Layer Security