Know what was checked
Canonical inputs, signed records, hashes, and reproducible verifier outputs make the Verification Data inspectable.
03 / Security
Trust is a stack of checks, not a single badge.
SDDT keeps Repository Assurance, cryptographic verification, hardware assurance, workload binding, release provenance, and independent review distinct. Verification answers whether required checks succeeded; assurance answers what confidence can legitimately be claimed.
Know what it proves
Vendor signatures and certificate chains can validate vendor-originated Hardware Evidence without proving that a specific preserved workload ran on that device.
Know what remains open
Missing freshness, provenance, workload binding, or review keeps the corresponding assurance gate closed.
Layered assurance
Each layer answers a different diligence question.
Security review should follow the claim chain from source to workload to outcome. The current posture is deliberately conservative.
Repository Assurance
Can the verifier and preserved repository artifacts be inspected and reproduced from the release?
RECORDEDCryptographic Verification
Do signatures, hashes, and vendor checks validate the bytes and records they cover?
REVIEWABLETier 3 GPU attestation binding
Status: BLOCKED_BY_VENDOR_PRIMITIVE_AVAILABILITY. Based on the documented public NVIDIA and Google interfaces reviewed as of October 2026, no supported primitive or API has been identified that cryptographically binds GPU attestation to a specific CUDA execution context or a specific workload output. Additional internal testing alone cannot establish Tier 3; a vendor-supported mechanism or a newly documented supported path from NVIDIA or Google is required.
Independent review
Has an independent party reviewed the complete chain and approved promotion beyond internal data?
PENDINGCurrent assurance boundary
GPU Gate (assurance promotion gate) remains CLOSED.
The recorded Google Confidential Space + Intel TDX + NVIDIA H100 result is PASS_NON_PROMOTABLE, classified as ATTESTED_WORKLOAD_AND_GPU_CORESIDENCE. Signature, GCE, GPU, and workload identities were verified, and a CUDA probe was observed. This does not prove authenticated execution of the specific CUDA workload or its output.
The Tier 3 binding status is BLOCKED_BY_VENDOR_PRIMITIVE_AVAILABILITY; GPU_GATE=CLOSED, B04=false, B05=false, and Tier3=false. Complete composite-profile qualification, provenance, and independent review remain separate requirements. The repository-local result marked INTERNAL_DEMO_ONLY is a different record, not the H100 run.
Public technical preview / prelaunch asset; production/Mainnet authorization and independent audit are not established.