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

7.6 Destroyed State

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
removed 7 Key States and Transitions part of 7

Title changed

Before · SP 800-57 Part 1 Rev. 4

Destroyed State

After · SP 800-57 Part 1 Rev. 5

Destroyed State

Control changed

Before · SP 800-57 Part 1 Rev. 4

The key has been destroyed as specified in Section 8.3.4 . Even though the key no longer exists when in this state, certain key metadata (e.g., key state transition history, key name, type, and cryptoperiod) may be retained for audit purposes (see Section 8.4 ). It is possible that a compromise of the destroyed key could be determined after the key has been destroyed. In this case, the compromise should be recorded.

After · SP 800-57 Part 1 Rev. 5

The key has been destroyed as specified in Section 8.3.4 . Even though the key no longer exists when in this state, certain key metadata (e.g., key state transition history, key name, type, and cryptoperiod) may be retained for audit purposes (see Section 8.4 ). It is possible that a compromise of the destroyed key could be determined after the key has been destroyed. In this case, the compromise should be recorded.