From 1334b84c2edcf9c7710b829fee759b7d22648fdc Mon Sep 17 00:00:00 2001 From: Adrian Stobbe Date: Wed, 13 Mar 2024 14:09:51 +0100 Subject: [PATCH] Update docs (#2982) Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> --- README.md | 2 +- docs/docs/architecture/attestation.md | 2 +- docs/versioned_docs/version-2.16/architecture/attestation.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 11e249216..5fa60301d 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ Encrypting your K8s is good for: ### 🔒 Everything always encrypted -* Runtime encryption: All nodes run inside AMD SEV-based Confidential VMs (CVMs). Support for Intel TDX will be added in the future. +* Runtime encryption: All nodes run inside Confidential VMs (CVMs) based on AMD SEV or Intel TDX. * Transparent encryption of network: All [pod-to-pod traffic is automatically encrypted][network-encryption] * Transparent encryption of storage: All writes to persistent storage are automatically encrypted. This includes [nodes' state disks][storage-encryption], [persistent volumes via CSI][csi], and [S3 object storage][s3proxy]. diff --git a/docs/docs/architecture/attestation.md b/docs/docs/architecture/attestation.md index 572a8511f..5e9523988 100644 --- a/docs/docs/architecture/attestation.md +++ b/docs/docs/architecture/attestation.md @@ -346,7 +346,7 @@ A user can [verify](../workflows/verify-cluster.md) this statement and compare t So far, this page described how an entire Constellation cluster can be verified using hardware attestation capabilities and runtime measurements. The last missing link is how the ground truth in the form of runtime measurements can be securely distributed to the verifying party. -The build process of Constellation images also creates the ground truth runtime measurements. +The build process of Constellation images also creates the ground truth runtime measurements. The builds of Constellation images are reproducible and the measurements of an image can be recalculated and verified by everyone. With every release, Edgeless Systems publishes signed runtime measurements. The CLI executable is also signed by Edgeless Systems. diff --git a/docs/versioned_docs/version-2.16/architecture/attestation.md b/docs/versioned_docs/version-2.16/architecture/attestation.md index 572a8511f..5e9523988 100644 --- a/docs/versioned_docs/version-2.16/architecture/attestation.md +++ b/docs/versioned_docs/version-2.16/architecture/attestation.md @@ -346,7 +346,7 @@ A user can [verify](../workflows/verify-cluster.md) this statement and compare t So far, this page described how an entire Constellation cluster can be verified using hardware attestation capabilities and runtime measurements. The last missing link is how the ground truth in the form of runtime measurements can be securely distributed to the verifying party. -The build process of Constellation images also creates the ground truth runtime measurements. +The build process of Constellation images also creates the ground truth runtime measurements. The builds of Constellation images are reproducible and the measurements of an image can be recalculated and verified by everyone. With every release, Edgeless Systems publishes signed runtime measurements. The CLI executable is also signed by Edgeless Systems.