# Raw Attestation

## General

We will call the basic (remote)-attestation that is supported by the Trusted Execution Environment (TEE) "Raw Attestation" in order to make clear that this is the baseline of attestation that is supported. For this attestation variant the processor takes measurements of the platform configuration and the initial configuration of the VM which includes the virtual firmware and the state of the vCPUs.

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

## AMD-SEV-SNP

In AMD-SEV-SNP the Raw Attestation process is one single step. In this single step the CPU takes the measurements of the firmware and the vCPUs and creates the attestation report. The report is signed through a private key that belongs to the CPU which has been certified through the AMD CA. A user can check the signature of the attestation report with the included public key and can contact the AMD CA with the public key and the certificate to validate that the platform is genuine.

## Intel TDX

The Raw Attestation process in Intel TDX is composed of two different steps. In a first step the CPU generates a structure that is called the TDREPORT. This report can only be verified on the the same platform and is therefore only used if VMs on the same CPU need to attest each other. For the remote verification this report is transformed into a TDQUOTE which is signed through the CPU with a key that can be checked through an Intel Service for its genuinity.


---

# 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.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.
