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 Key Change 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

Title

Key Change Function

Control changed

Before · SP 800-57 Part 1 Rev. 4

Key change is the replacement of a key with another key that performs the same function as the original key. There are several reasons for changing a key. 1. The key may have been compromised, 2. The key’s cryptoperiod may be nearing expiration, or 3. It may be desirable to limit the amount of data protected with any given key.

After · SP 800-57 Part 1 Rev. 5

Key change is the replacement of a key with another key that performs the same function as the original key. There are several reasons for changing a key.: 1. The key may have been compromised, 2. The key’s cryptoperiod may be nearing expiration, or

100 This could be the case when performing a key-establishment process for some key-establishment schemes (see SP 800-56A and SP 800-56B). 3. It may be desirable to limit the amount of data protected with any given key.