> For the complete documentation index, see [llms.txt](https://docs.enclaive.cloud/confidential-cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enclaive.cloud/confidential-cloud/technology-in-depth/intel-sgx/vault-remote-attestation-plug-in/initialization.md).

# Initialization

<figure><img src="https://lh5.googleusercontent.com/eArNwzAGNXjGU-U1-ESo0b9WmpuCrsdSkzOY89Z-45o3WnDabfLo5Q8hAmybN8xX6RWZJiw7Q1rFNUzWEneibHvhmkFlIt7Ecb7RBGXDuTly3L-XVY4f7kvjGROuET8CLq-jd-tL84qMB4yQCaMHhoQ" alt=""><figcaption><p>Vault Initialization Workflow</p></figcaption></figure>

The attestation encompasses the certificate's hash used for servicing the request. The administrator can establish a secure TLS channel into the enclave with remote attestation by verifying the attestation using the received peer certificate.

Upon successfully delivering a specified number of quotes to external users (currently set to one), the premain process terminates and triggers the execution of the vault. The vault, in turn, utilizes the previously generated certificate for subsequent secure communication.

The vault is configured to rely on this particular certificate for trust verification, utilizing the previously attested channel. Subsequent unsealing of the vault operator is performed confidentially and can potentially be automated.

It is worth noting that incorporating the premain logic into the plugin for enhanced flexibility is not feasible without modifying the vault's source code. This limitation arises because plugins are only loaded after unsealing, which already necessitates a secret.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.enclaive.cloud/confidential-cloud/technology-in-depth/intel-sgx/vault-remote-attestation-plug-in/initialization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
