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

2.2.2.2 Non-Critical Data

NIST platform security: roots of trust, firmware and secure enclaves SP 800-193
All changes in this version
first version loaded 2 Platform Architecture part of 2.2.2

Title

Non-Critical Data

Control

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 during boot
• State: State settings which do not affect the integrity of the platform Examples: The state of the Num Lock key upon system boot; whether the BIOS performs a fast boot or standard boot

Non-critical data should not be critical to the secure booting or operation of a platform. In practice, all data consumed by platform firmware may be security-sensitive, including some data that does not directly impact the correct and secure operation of the platform. Errors or malicious attacks in any data consumed by platform firmware could expose and exploit vulnerabilities in that code. As such, particular care needs to be given to any non-trusted input or data consumed by the platform.