You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li><p>Requesting secrets directly from workloads</p></li>
423
423
</ul>
424
-
<p>When a workload requires a secret, such as a key to decrypt a container image or model, guest components collect hardware evidence from the active CPU and GPU enclaves. The evidence is sent to Trustee, the remote verifier in Confidential Containers deployments. Trustee evaluates the evidence against known-good reference values and configured policies, and conditionally releases the requested resource.</p>
424
+
<p>When a workload requires a secret, such as a key to decrypt a container image or model, guest components collect hardware evidence from the active CPU and GPU enclaves.
425
+
The evidence is sent to the remote verifier to evaluate the evidence against known-good reference values and configured policies, and conditionally releases the requested resource.</p>
425
426
<sectionid="key-concepts">
426
427
<h2>Key Concepts<aclass="headerlink" href="#key-concepts" title="Permalink to this headline">#</a></h2>
427
428
<p>The following concepts appear throughout this page:</p>
428
429
<ulclass="simple">
429
-
<li><p>Confidential Containers (CoCo): The open-source project that implements the cloud-native approach to Confidential Computing. CoCo uses Kata Containers as the sandbox and Trustee as the attestation framework. Refer to the upstream <aclass="reference external" href="https://confidentialcontainers.org/docs/">Confidential Containers documentation</a> for project background and attestation best practices.</p></li>
430
+
<li><p>Confidential Containers (CoCo): The open-source project that implements the cloud-native approach to Confidential Computing.
431
+
CoCo uses Kata Containers as the sandbox and Trustee as the attestation framework.</p></li>
430
432
<li><p>Trusted Execution Environment (TEE): A hardware-isolated environment, such as AMD SEV-SNP, Intel TDX, or an NVIDIA Confidential Computing GPU, that protects code and data in use.</p></li>
431
433
<li><p>Remote attestation: The process of cryptographically proving to a remote party that a TEE is running the expected, untampered software stack before that party releases secrets to it.</p></li>
432
434
<li><p>Trustee: The remote verifier in the Confidential Containers attestation flow. Trustee is composed of three cooperating services:</p>
@@ -439,19 +441,21 @@ <h2>Key Concepts<a class="headerlink" href="#key-concepts" title="Permalink to t
439
441
<li><p>KBS resource: A secret, for example, a key, credential, or token, that Trustee releases to a guest when attestation succeeds. Most resources are addressed by a three-part path: <codeclass="docutils literal notranslate"><spanclass="pre"><repository>/<type>/<tag></span></code>.</p></li>
440
442
<li><p>Policy: The rule set that Trustee evaluates against verified evidence to decide whether to release a resource. By default, Trustee denies resource requests from clients that have not presented valid TEE evidence.</p></li>
441
443
</ul>
444
+
<p>Refer to the upstream <aclass="reference external" href="https://confidentialcontainers.org/docs/architecture/design-overview/">Confidential Containers documentation</a> for more details on these concepts and attestation best practices.</p>
442
445
</section>
443
446
<sectionid="quickstart">
444
447
<h2>Quickstart<aclass="headerlink" href="#quickstart" title="Permalink to this headline">#</a></h2>
445
448
<p>This page walks you through standing up a development Trustee instance with Docker Compose, installing the Key Broker Service (KBS) client tool, and sending a sample resource request to confirm the system is reachable.
446
-
The goal is to give you a working attestation backend and a client you can use to interact with it before you wire it into a Confidential Containers workload.</p>
447
-
<p>This page is for new users who want to try out attestation on a single Linux host.
448
-
For a deeper explanation of attestation, Trustee, and the full set of features, refer to the upstream <aclass="reference external" href="https://confidentialcontainers.org/docs/attestation/">Attestation</a> and <aclass="reference external" href="https://confidentialcontainers.org/docs/features">Features</a> sections of the Confidential Containers documentation.</p>
449
-
<p>This quickstart runs on a standalone Linux host and does not require a Kubernetes cluster or the Confidential Containers runtime to complete.
450
-
In a real deployment, attestation builds on the runtime setup described in the <aclass="reference internal" href="confidential-containers-deploy.html"><spanclass="doc">Confidential Containers deployment guide</span></a>. Confidential workloads use Trustee to cryptographically verify their TEE before they receive secrets, encrypted container images, authenticated registries, or other sensitive resources.</p>
449
+
It runs on a standalone Linux host and does not require a Kubernetes cluster or the Confidential Containers runtime.</p>
450
+
<p>The goal is to give you a working local attestation backend and a client to interact with it before you wire Trustee into a Confidential Containers workload.</p>
451
451
<divclass="admonition note">
452
452
<pclass="admonition-title">Note</p>
453
-
<p>This quickstart is for development and evaluation only. Do not use the Trustee instance you stand up here in production.
454
-
This guide does not deploy a Trusted Execution Environment (TEE), does not produce real hardware attestation evidence, and does not release any secrets to a workload. It only validates that the Trustee components are running and reachable.
453
+
<p>This quickstart is for evaluation only.
454
+
Do not use the Trustee instance you stand up here in production.
455
+
This guide does not deploy a TEE, does not produce real hardware attestation evidence, and does not release any secrets to a workload.
456
+
It only validates that the Trustee components are running and reachable.</p>
457
+
<p>A production attestation workflow depends on your environment and your organization’s security policies.
458
+
Documenting a full attestation workflow is outside the scope of this quickstart.
455
459
To run attestation against real evidence from a confidential workload, refer to the upstream <aclass="reference external" href="https://confidentialcontainers.org/docs/attestation/">Attestation</a> and <aclass="reference external" href="https://confidentialcontainers.org/docs/features">Features</a> documentation for more information.</p>
0 commit comments