BaselineWatch
47 requirements
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

NIST platform security: roots of trust, firmware and secure enclaves SP 800-193

47 requirements · published 2018-05-04
Changes in this version
All1 Introduction2 Platform Architecture3 Principles and Key Concepts4 Firmware Security Guidelines for Platform Devices
RefTitleText
2 Platform Architecture Ensuring a platform’s firmware code and critical data are always in a state of integrity is critical to ensure that a computing system can be operated free from malware. Modern client and server computing systems can be considered to be sep
2.1
in 2
 Platform Devices As noted above, the platform is a collection of devices that provide the functional capabilities and services needed by the operating system and applications. While resiliency of the platform as a whole is the ultimate objective, it is impo
2.2
in 2
 Code and Data in Platform Devices The devices described above will typically contain some set of firmware and data on nonvolatile storage, either resident on the device itself or on a shared storage device (e.g., the SPI flash). This section describes firmware code and data
2.2.1
in 2.2
 Code Firmware code is the set of instructions used by any device’s processing unit to perform the operations required by the device. Historically, firmware in platform devices has rarely been modified in the field, although system or component v
2.2.2
in 2.2
 Data Data are pieces of information that Platform Firmware code uses to carry out its operation, as instructed by the code. Data can be further categorized as critical and non-critical. Critical data includes configuration settings and policies
2.2.2.1
in 2.2.2
 Critical Data Critical data may be used for various purposes, including: • Configuration settings: Data which tells the code how to configure operational aspects of the device Example: Enabling a peripheral that is disallowed by enterprise security polic
2.2.2.2
in 2.2.2
 Non-Critical Data Non-critical data may be used for various purposes, including: • Informational / UI: Data which is merely informational or used as part of a user interface (UI) for the end user Example: An asset tag name of “Property of NIST” is displayed

7 of 47.