CSPACE-IMG-01: Workload image signing is enforced and the registry is not plantable¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | attest |
| Policy | P-09: Only signed images pinned to a measurement are launched |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- Image signing is enforced and the workload image is digest-pinned.
How to fix¶
- Set tee-signed-image-repos and cosign-sign the workload image, reference it by @sha256 digest, and scope Artifact Registry write to CI only. Consider Binary Authorization for the project.
- Set tee-signed-image-repos, cosign-sign the image, pin by @sha256, and scope Artifact Registry write to CI only.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- Need --gcp-instance, --gcp-zone, and --gcp-project; skipping check.
ERROR:
- Could not read image-signing inputs: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gcp-instance |
Confidential VM instance name. |
--gcp-project |
GCP project ID. |
--gcp-zone |
Zone of the Confidential VM. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| Google Cloud | artifactregistry.projects.locations.repositories.getIamPolicy |
artifactregistry.repositories.getIamPolicy |
read |
| Google Cloud | compute.instances.get |
compute.instances.get |
read |
See Required permissions for every check on this platform.
Related¶
- Other checks for policy P-09: AZ-MEAS-01, CCA-MEAS-01, CSPACE-BINAUTHZ-01, CSPACE-IMG-02, GPU-RIM-01, REG-PROV-01, REG-SIG-01, REG-SIG-02, SE-MEAS-01, SGX-MEAS-01, SNP-MEAS-01, TDX-MEAS-01
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).