Vendor-specific verification
SEV-SNP, SGX DCAP, TDX, and Arm CCA have different report formats and trust chains. Support is verified per vendor instead of hidden behind one generic “secure” badge.
Hardware evidence for compute
Check the environment behind the result.
Sigil’s TEE verification checks supported hardware attestations against the network’s approved trust material and measurements.
TEE VerificationIllustrated study
Source / fingerprint / attribution
An anchor identifies a record. It does not prove every claim.
01 / Built for a purpose
A provider’s signature is only the beginning.
Trusted execution environments can add evidence about the hardware and measured environment used for a workload. Sigil treats that evidence as something to verify against an explicit policy, with a separate path for each supported attestation format.
Approved measurements
A valid report still needs to match the environment the consumer intended to use. Network policy defines the measurements and identities that can be accepted.
Pinned roots of trust
Verification depends on the relevant vendor keys and certificate material. Cryptographic checks connect a report to the trust roots configured for that network.
Reject incomplete evidence
Missing verification support, disabled policy, unsupported vendors, and failed cryptographic checks prevent TEE receipt settlement.
The details matterGood questions.
Good questions.
Clear answers.
Is TEE attestation a proof that the output is correct?
Attestation provides evidence about a measured execution environment under a hardware trust model. Correctness still depends on the measured software, workload binding, and the application’s verification policy.
Are all listed TEE platforms available on every network?
No. The list describes verifier capabilities. Current provider availability and accepted measurements must be checked against the network you intend to use.
Keep exploringOne capability.