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.1 Solution Overview

NIST platform security: roots of trust, firmware and secure enclaves IR 8320A
All changes in this version
first version loaded 3 During workload orchestration, periodically audit the asset tag of the cloud server platform part of 3

Title

Solution Overview

Control

This stage of the use case enables the creation of what are called trusted compute pools . Also known as trusted pools , they are physical or logical groupings of computing hardware in a data center that are tagged with specific and varying security policies, and the access and execution of apps and workloads are monitored, controlled, audited, etc. In this phase of the solution, an attested launch of the platform is deemed as a trusted node and is added to the trusted pool.

Figure 1 depicts the concept of trusted pools. The resources tagged green indicate trusted ones. Critical policies can be defined such that security-sensitive cloud services can only be launched on these trusted resources.

Figure 1: Concept of Trusted Compute Pools In order to have a trusted launch of the platform, the two key questions that should be answered are: