CSPACE-LAUNCH-01: Workload launch policy forbids host env/command override¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | deploy |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- Launch policy pins env/command: the launcher refuses host-supplied tee-env-*/tee-cmd.
How to fix¶
- Rebuild the workload image without tee.launch_policy.allow_env_override / allow_cmd_override (and allow_capabilities) so the Confidential Space launcher refuses operator-supplied tee-env-*/tee-cmd. Bake required configuration into the signed image rather than passing it through VM metadata.
- Rebuild the workload image without tee.launch_policy.allow_env_override/allow_cmd_override; bake configuration into the signed image instead of passing it through VM metadata.
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 the workload image launch policy: …
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 | compute.instances.get |
compute.instances.get |
read |
See Required permissions for every check on this platform.
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).