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

3.2 Resiliency Properties

NIST platform security: roots of trust, firmware and secure enclaves SP 800-193
All changes in this version
first version loaded 3 Principles and Key Concepts part of 3

Title

Resiliency Properties

Control

The technical guidelines in this document are written in terms of guidelines for individual platform devices in order to make them broadly applicable to a variety of devices, platforms and systems. Despite the narrow focus on devices, the intent of this document is to establish guidelines supporting overall resiliency in systems against destructive attacks by ensuring that the underlying platform is resilient.

Platforms may not be able to fully provide the protection, detection and recovery capabilities for all platform devices. A loss of functionality in even one device may be sufficient to render the complete system permanently inoperable if that particular device plays a crucial role in booting or operating the platform. For a platform as a whole to claim resiliency to destructive attacks, the set of platform devices necessary to minimally restore operation of the system, and sufficient to restore reasonable functionality, should themselves be resilient. We call this set of devices critical platform devices . The particular resiliency properties may vary from platform-to- platform.

Protected For a platform to be considered Protected , all critical platform devices must meet the protection guidelines found in Sections 4.1 and 4.2 , but may not fully offer capabilities to recover the device’s firmware and/or critical data.

Recoverable For a platform to be considered Recoverable , all critical platform devices must provide the means to detect corruption as described in Sections 4.1 and 4.3 , and provide the means to recover from this corruption in compliance with the guidelines in Sections 4.1 and 4.4 .

Resilient For a platform to be considered Resilient , all critical platform devices must meet all of the guidelines in Section 4 . Non-critical devices should also meet these requirements or at least be designed such that a compromise of one of these devices will not impact the security of the platform as a whole. Resilient platforms will attempt to prevent attacks capable of disrupting the correct operation of the platform, while also providing mechanisms to detect and recover from malicious of accidental problems that occur.