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.2 Continuity of Operations Function

NIST platform security: roots of trust, firmware and secure enclaves SP 800-57 Part 1 Rev. 4
All changes in this version
first version loaded 8 Key-Management Phases and Functions part of 8.2

Title

Continuity of Operations Function

Control

Keying material can become lost or unusable, due to hardware damage, corruption or loss of program or data files, system policy, or configuration changes. In order to maintain the continuity of operations, it is often necessary for users and/or administrators to be able to recover keying materials from backup storage. However, if operations can be continued without the backup of keying material (e.g., by re-keying), or the keying material can be recovered or reconstructed without being saved, it may be preferable not to save the keying material in order to lessen the possibility of a compromise of the keying material or other cryptographically related information. The compromise of keying material affects the continuity of operations (see Section 8.4 ). When keying material is compromised, the continuity of operations requires the establishment of entirely new keying material (see Section 8.1.5 ), following an assessment of what keying material is affected and needs to be replaced.