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

4.2.5.3 Security Properties of the Key-Establishment Schemes

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 4 Cryptographic Algorithms part of 4.2.5

Title changed

Before · SP 800-57 Part 1 Rev. 4

Security Properties of the Key-Establishment Schemes

After · SP 800-57 Part 1 Rev. 5

Security Properties of the Key-Establishment Schemes

Control changed

Before · SP 800-57 Part 1 Rev. 4

Cryptographic protocol designers need to understand the security properties of the schemes in order to assure that the desired capabilities are available to the user. In general, schemes where each party uses both an ephemeral and a static key provide more security properties than schemes using fewer keys. However, it may not be practical for both parties to use both static and ephemeral keys in certain applications. For example, in email applications, it is desirable to send messages to other parties who are not on-line; in this case, the receiver cannot be expected to provide an ephemeral key to establish the message-encrypting key during a [SP800-56A] key-agreement scheme. For the schemes in [SP800-56B] , ephemeral keys are never used. Both [SP80056A] and [SP800-56B] include discussions of the security properties of each of its schemes.

After · SP 800-57 Part 1 Rev. 5

Cryptographic protocol designers need to understand the security properties of the schemes in order to assure that the desired capabilities are available to the user. In general, schemes where each party uses both an ephemeral and a static key provide more security properties than schemes using fewer keys. However, it may not be practical for both parties to use both static and ephemeral keys in certain applications. For example, in email applications, it is desirable to send messages to other parties who are not on-line; in this case, the receiver cannot be expected to provide an ephemeral key to establish the message-encrypting key during a [SP800-56A] key-agreement scheme. For the schemes in [SP800-56B] , ephemeral keys are never used. Both [SP80056A] and [SP800-56B] include discussions of the security properties of each of its schemes.