To learn more about using attestation assertions, see Create an attestation policy.
The available assertions to construct an attestation policy are detailed in the following table. They can validate assertions made by the Confidential Space image, the workload container, and the VM.
Image assertions
Assertion | Type | Description |
---|---|---|
Interacts with:
|
Defined string |
Verifies that the Confidential Space image is the debug or production version. The valid values are:
ExamplesThe following code verifies that the debug version of the Confidential Space image is being used:
The following code verifies that the production version of the Confidential Space image is being used:
|
assertion.submods.confidential_space.support_attributes |
String array |
Verifies the security version of the TEE is a production Confidential Space image. Debug Confidential Space images have no support attribute set. There are three support attributes:
ExampleThe following code verifies that a stable version of the Confidential Space image is being used:
|
assertion.swname |
Defined string |
Verifies the software running on the attesting entity. The
value is always Example
|
assertion.swversion |
String array |
Verifies the software version of the Confidential Space image. We
recommend using
Example
|
Container assertions
Assertion | Type | Description |
---|---|---|
Interacts with:
|
String array |
Verifies the CMD commands and parameters used in the workload image. ExamplesThe following code verifies the CMD of the workload image hasn't been overwritten:
The following code verifies that
|
Interacts with:
|
JSON object |
Verifies that environment variables and their values have been explicitly passed to the container. ExampleThe following code verifies that the environment variable
|
Interacts with:
|
String |
Verifies if the workload operator has overwritten environment variables in the container. ExamplesThe following code verifies that the workload operator has not
overridden the
The following code verifies that the workload operator hasn't overwritten any environment variables:
|
assertion.submods.container.image_digest |
String |
Verifies the image digest of the workload container. Specifying this condition lets multiple parties agree on an authorized workload that is allowed to access their data. Example
|
assertion.submods.container.image_id |
String |
Verifies the image ID of the workload container. Example
|
Interacts with:
|
String |
Verifies the location of the workload container running on top of the Confidential Space image. Example
|
Interacts with:
|
JSON object |
Verifies that the image has a certain signature or is signed by a public key and signing algorithm. Specifying this condition lets multiple parties agree on an authorized workload that is allowed to access their data. The assertion can include the following elements:
Example
|
Interacts with:
|
Defined string |
Verifies the restart policy of the container launcher for when the workload stops. The valid values are:
Example
|
VM assertions
Assertion | Type | Description |
---|---|---|
Interacts with:
|
String array |
Verifies that a specified service account is connected to the
VM running the workload, or has been listed using
Example
|
assertion.hwmodel |
String |
Verifies the underlying Confidential Computing technology. The supported platforms are as follows:
Example
|
Interacts with:
|
Boolean |
Verifies the monitoring state on the attesting entity. Example
|
assertion.submods.gce.instance_id |
String |
Verifies the VM instance ID. Example
|
assertion.submods.gce.instance_name |
String |
Verifies the name of the VM instance. Example
|
assertion.submods.gce.project_id |
String |
Verifies that the VM is running a Google Cloud project with the specified project ID. Example
|
assertion.submods.gce.project_number |
String |
Verifies that the VM is running in a Google Cloud project with the specified project number. Example
|
Interacts with:
|
String |
Verifies that the VM is running in the specified zone. Example
|