# Raw Attestation with Secure-Boot

## General

Secure-Boot itself is a standalone component of the UEFI stack that is designed to protect the pre-boot process. It therefore contains a list of binaries that are allowed to run during the boot process. As the Raw Attestation only protects the firmware and the initial platform configuration this can be seen as the next step in securing the platform. In a first step the Raw Attestation measures the firmware which includes the UEFI Secure-Boot component. Afterwards the boot process continues and the measurements stored for Secure-Boot are compared with the taken measurements. An attesting party can be sure that when the measurements of the firmware retrieved via the Raw Attestation process are correct that also Secure-Boot has been executed successfully. Subsequently the complete boot process including the kernel have been secured and it is possible to detect the manipulation of the boot process.

<img src="/files/DQPRna0A97YXWJx5ZvuA" alt="" class="gitbook-drawing">

## AMD-SEV-SNP

* [x] Supported

## Intel TDX

* [x] Supported


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.enclaive.cloud/confidential-cloud/technology-in-depth/attestation-methods/raw-attestation-with-secure-boot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.