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.1 Re-keying

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

Re-keying

Control changed

Before · SP 800-57 Part 1 Rev. 4

If the new key is generated in a manner that is entirely independent of the “value” of the old key, the process is known as re-keying. This replacement shall be accomplished using one of the key-establishment methods discussed in Section 8.1.5 . Re-keying is used when a key has been compromised (provided that the re-keying scheme itself is not compromised) or when the cryptoperiod is nearing expiration.

After · SP 800-57 Part 1 Rev. 5

If the new key is generated in a manner that is entirely independent of the “value” of the old key, the process is known as re-keying. This replacementReplacement shall be accomplished using one of the key-establishmentkey- establishment methods discussed in Section 8.1.5 . Re-keying is used when a key has been compromised (provided that the re-keying scheme itself is not compromised) or when the cryptoperiod has expired or is nearing expiration.