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.5 Key Confirmation

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

Title

Key Confirmation

Control

Key confirmation is used by two parties in a key-establishment process to provide assurance that common keying material and/or a shared secret 5 has been established. The assurance may be provided to only one party (unilateral) or it may be provided to both parties (bilateral). The assurance may be provided as part of the key-establishment scheme, or it may be provided by some action that takes place outside of the scheme. For example, after a key is established, two parties may provide assurance (i.e., a confirmation) to one another that they possess the same key by demonstrating their ability to encrypt and decrypt data intended for each other. [SP800-56A] provides for unilateral key confirmation for schemes where one party has a static key-establishment key, and bilateral key confirmation for schemes where both parties have static key-establishment keys. A total of ten key-confirmation schemes are provided, seven of which are unilateral, and three of which are bilateral. [SP800-56B] provides for unilateral key confirmation from the responder, in the case of a key agreement scheme, and from the receiver, in the case of a key-transport scheme. Initiator and bilateral key confirmation are also provided for one family of key-agreement schemes.

5 An intermediate value computed during a key-agreement scheme.