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.3.4 Key Destruction 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.3

Title

Key Destruction Function

Control changed

Before · SP 800-57 Part 1 Rev. 4

When copies of cryptographic keys are made, care should be taken to provide for their eventual destruction. All copies of the private or symmetric key shall be destroyed as soon as they are no longer required (e.g., for archival or reconstruction activity) in order to minimize the risk of a compromise. Keys shall be destroyed in a manner that removes all traces of the keying material so that it cannot be recovered by either physical or electronic means 45 . Public keys may be retained or destroyed, as desired.

After · SP 800-57 Part 1 Rev. 5

When copies of cryptographic keys are made, care should be taken to provide for their eventual destruction (e.g., the identity of sharing parties could be recorded in the key’s metadata). All copies of thea private or secret (symmetric) key shall be destroyed as soon as they are no longer required (e.g., for archival or reconstruction activity) in order to minimize the risk of a compromise. KeysSecret and private keys shall be destroyed in a manner that removes all traces of the keying materialkeys so that itthey cannot be recovered by either physical or electronic means 45 . 103 Public keys may be retained or destroyed, as desired.