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

9.5.3.1 General Principles

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
added 9 Additional Considerations part of 9.5.3

Title changed

Before · SP 800-57 Part 1 Rev. 4

After · SP 800-57 Part 1 Rev. 5

General Principles

Control changed

Before · SP 800-57 Part 1 Rev. 4

After · SP 800-57 Part 1 Rev. 5

Planning for recovery from system failures is an essential management function. Interruptions of critical infrastructure services should be anticipated, and planning for maintaining the continuity of operations in support of an organization’s primary mission requirements shall be done. With respect to key management, the following situations are typical of those for which planning is necessary: 1. Lost key cards or tokens; 2. Forgotten authenticators (e.g., tokens or passwords) that control access to keys; 3. The failure of key-input devices (e.g., readers, PIV cards); 4. The loss or corruption of the memory media on which keys and/or certificates are stored; 5. The compromise of keys; 6. Certificate termination without replacement certificates being installed; 7. The corruption of Certificate Revocation Lists (CRLs) or Compromised Key Lists (CKLs); 8. Hardware failure of key or certificate generation, registration, and/or distribution systems, subsystems, or components;