Quick Start
Quick Start to deploy the Attestation Service
The Attestation Service (AS or CoCo-AS) verifies hardware evidence. The AS was designed to be used with the Key Broker Service (KBS) for Confidential Containers, but it can be used in a wide variety of situations. The AS can be used anytime TEE evidence needs to be validated.
Today, the AS can validate evidence from the following TEEs:
┌───────────────────────────────────┐
┌───────────────────────┐ Evidence │ Attestation Service │
│ ├────────────►│ │
│ Verification Demander │ │ ┌───────────┐┌──────────────────┐ │
│ (Such as KBS) │ │ │┌────────┐ ││ Reference Value │◄┼────Reference Value
│ │◄────────────┤ ││ Policy │ ││ Provider Service │ │
└───────────────────────┘ Attestation │ ││ Engine │ │└──────────────────┘ │
Results Token │ │└────────┘ │ │
│ │Attestation│ │
│ │ Token │ ┌────────────────┐ │
│ │ Broker │ │Verifier Drivers│ │
│ └───────────┘ └────────────────┘ │
└───────────────────────────────────┘
The Attestation Service (AS) has a simple API. It receives attestation evidence and returns an attestation token containing the results of a two-step verification process. The AS can be consumed directly as a Rust crate (library) or built as a standalone service, exposing a REST or gRPC API. In Confidential Containers, the client of the AS is the Key Broker Service (KBS), but the evidence originates from the Attestation Agent inside the guest.
The AS has a two-step verification process.
The first step is accomplished by one of the platform-specific Verifier Drivers. The second step is driven by the Attestation Token Broker with help from the Reference Value Provider Service (RVPS).
Quick Start to deploy the Attestation Service