Skip to content

Conversation

@FilipCivljak
Copy link

Type of PR

Documentation update – adds explanation of Cube AI attestation, Attested TLS (aTLS), and Local Proxy-based attestation.

What this does

  • Adds a general overview of attestation and why it matters
  • Explains how Cube AI uses Attested TLS (aTLS) for secure communication
  • Details how the Local Proxy automates attestation for users
  • Describes attestation policy verification and security guarantees
  • Improves clarity and readability of the attestation documentation

Related Issues

  • NOISSUE (documentation improvement)

Tests

  • No, this PR only updates documentation

Notes

aTLS is a standard TLS connection augmented with a **hardware-backed attestation report** proving that the remote service is running inside a **Trusted Execution Environment (TEE)**.

During startup:
In Cube AI, the Embeddings Service acts as the TLS server and extends its **X.509 certificate** with an attestation report generated by the underlying TEE (e.g. AMD SEV-SNP).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we dont have an "embeddings service"

---

## Why Attestation Matters
## Local Proxy-Based Attestation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

our proxy sits on the cloud, users don't deploy it. atls can be verifid through audit logs and attestation can be still fetched directly using proxy

The Local Proxy enforces an **attestation policy** that defines the expected properties of the TEE.

### 🔹 Attestation Endpoint
This policy includes:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

insert a sample attestation policy json file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants