BaselineWatch
Desk

4.1.1 Roots of Trust (RoT) and Chains of Trust (CoT)

NIST platform security: roots of trust, firmware and secure enclaves SP 800-193
All changes in this version
first version loaded 4 Firmware Security Guidelines for Platform Devices part of 4.1

Title

Roots of Trust (RoT) and Chains of Trust (CoT)

Control

1) The security mechanisms shall be founded in Roots of Trust (RoT). 2) If Chains of Trust (CoT) are used, a RoT shall serve as the anchor for the CoT. 3) All RoTs and CoTs shall either be immutable or protected using mechanisms which ensure all RoTs and CoTs remain in a state of integrity. 4) All elements of the Chains of Trust for Update, Detection and Recovery in non-volatile storage shall be implemented in platform firmware. Note: This guideline that RoTs and CoTs be implemented as part of platform firmware applies only to elements that implement the platform resiliency functions described in this paper. Platform vendors are encouraged to maintain a chain of trust from boot firmware through the Operating System to provide resiliency against various forms of attacks.

5) The functions of the RoTs or CoTs shall be resistant to any tampering attempted by software running under, or as part of, the operating system on the host processor. 6) Information transferred from the software on the host processor to the platform firmware shall be treated as untrusted. 7) CoTs may be extended to include elements that are not from non-volatile storage. Before use, those elements shall be cryptographically verified by an earlier element of the CoT. 8) RoTs and CoTs that cross device boundaries, or that provide services to a symbiont device, shall use a secure communication channel between devices.