CSPACE-DEBUG-01: Confidential Space runs the hardened production image with debug off¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | deploy |
| Policy | P-05: No debug TEEs in production |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- Runs the hardened production CS image with log redirect off.
How to fix¶
- Launch from the production Confidential Space image (not the -debug variant) and disable tee-container-log-redirect so the workload's output stays inside the TEE.
- Launch from the production Confidential Space image (not -debug) and disable tee-container-log-redirect so workload output stays in the TEE.
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 instance image/metadata: …
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.
Related¶
- Other checks for policy P-05: CCA-POL-01, SE-POL-01, SGX-POL-01, SNP-POL-01, TDX-POL-01
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).