untrust documentation¶
untrust audits the trust boundaries that attestation does not cover in confidential computing deployments: the bootstrap state a workload loads from outside, the host-supplied configuration it trusts, and the key-release policies that should, but often do not, require attestation.
Hardware attestation proves which code booted. It says nothing about the object a workload downloads at boot, the environment file the host hands it, or a key policy that releases secrets without checking a measurement. untrust checks those inputs and reports each one as PASS, FAIL or not assessed, with remediation for every failure.
Two ways to run it¶
-
On the command line. Install the
untrustCLI, rununtrust scan --demoto see a report without any cloud credentials, then scan your own deployment with your own read-only credentials. Gate builds and infrastructure changes in CI withuntrust buildscananduntrust iacscan. Install the CLI -
In the hosted console. At app.untrustsecurity.com your organization collects scan reports, CI evidence, collector evidence from your confidential hosts and runtime detections in one place, rolls them up into policies and compliance frameworks, and exports signed evidence packs. Get started with the console
The two are the same scanner. A cloud scan is a local scan plus an upload: the CLI runs where your credentials already are, and the console stores and evaluates what you send it. See how the CLI and the console fit together.
Platforms¶
| Platform | What untrust inspects |
|---|---|
| AWS Nitro Enclaves | The enclave's bootstrap state store (S3 and alternative backends), the KMS key policy that should require attestation, the parent instance's host configuration, and the running enclave's measurements. |
| GCP Confidential Space (AMD SEV-SNP) | Workload Identity Federation conditions that gate Cloud KMS, the bootstrap bucket, the Confidential VM configuration, the attestation token, and paths that bypass attestation. |
| Azure confidential VMs | Confidential VM size and security type, Secure Boot and vTPM, confidential OS-disk encryption, the Secure Key Release policy and the Microsoft Azure Attestation provider. |
| NVIDIA GPU Confidential Computing | GPU attestation reports, verifier policy, CC mode, attestation ordering, model inputs and the binding between the GPU and its confidential VM. |
| Hardware fleets | Signed evidence from enrolled collectors on SEV-SNP, TDX, SGX, Arm CCA, Nitro Enclaves and IBM Secure Execution hosts, verified against vendor trust roots. |
| Image registries | Whether deployed artifacts are pinned by digest, signed by a trusted identity and bound to the measurements your key policies trust. |
Each platform has a step-by-step setup guide. The check reference gives every check its own page, and Required permissions lists exactly what each scan calls. Both are generated from the scanner itself.
When something doesn't look right, start with Troubleshooting or the FAQ. New terms are defined in the Glossary.
The rule untrust never breaks¶
Unknown never becomes PASS. A check that was skipped, that errored, or that never ran is reported as not assessed. It is never counted toward a pass, a policy, a compliance control or a release gate. Read Concepts for what each verdict means.