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

8.2.3.2 Key Update Function

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 8 Transition: A transition plan should be developed and followed so that the changeover part of 8.2.3

Title

Key Update Function

Control changed

Before · SP 800-57 Part 1 Rev. 4

If the “value” of the new key is dependent on the value of the old key, the process is known as key update (i.e., the current key is modified to create a new key). Key update is a special case of key derivation (see Section 8.2.4 ), where the derived key replaces the key used to derive it. For example, suppose that K 1 is used as an encryption key. When K 1 needs to be replaced, it is used to derive K 2. K 2 is then used as the new encryption key until it is replaced by K 3, which is derived from K 2. Key update could result in a security exposure if an adversary obtains a key in the chain of keys and knows the update process used; keys subsequent to the compromised key could easily be determined. Federal applications shall not use key update (also, see [ SP800-152 ]).

After · SP 800-57 Part 1 Rev. 5

If the “value” of the new key is dependent on the value of the old key, the process is known as key update (i.e., the current key is modified to create a new key). Key update is a special case of key derivation (see Section 8.2.4 ), where the derived key replaces the key used to derive it. For example, suppose that K 1 is used as an encryption key. When K 1 needs to be replaced, it is used to derive K 2. K 2 is then used as the new encryption key until it is replaced by K 3, which is derived from K 2. Key update could result in a security exposure if an adversary obtains a key in the chain of derived keys and knows the update process that was used; keys subsequent to the compromised key could easily be determined. Federal applications shall not use key update (also, see [SP SP800-152800-152 ]).