feat(experiments): hardware TEE attestation experiment runner#357
Merged
Conversation
Adds experiments/claim-hw-attestation: the one experiment that exercises the real hardware path (genuine attestation report, nonce binding, raw-evidence verification, end-to-end TRACE Claim verification) instead of software-only mode. Safe everywhere: SKIPs with exit 0 when no TEE is detected, so CI and dev hosts pass. Produces results only on a confidential VM (SEV-SNP / TDX / TPM). README documents the Azure/GCP deploy -> config -> run -> verify sequence and the cert-chain appraisal (AMD KDS / Intel DCAP / TPM EK) that remains as the last hardware-dependent step. Uses the gateway's real nonce construction (JWK thumbprint || salt) so the verifier's key-binding check passes on hardware.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
experiments/claim-hw-attestation/— the experiment that exercises the real hardware TEE path, so everything is ready to run the moment a confidential VM is available.Every other experiment runs software-only (
attestation_assurance: none). This one:report.report_dataequals the gateway-supplied noncereport_data(freshness)Safe everywhere
On a host with no TEE it prints
SKIPand exits 0 — verified on this (non-TEE) machine. CI scope (ruff check src/ tests/,mypy src/,pytest tests/unit) is untouched, so nothing new can break the build.experiments/is not in the lint scope (same as the other runners).Uses the real APIs
Drives
detect/get_attestation_report(cmcp_runtime.tee),generate_trace_claim(cmcp_runtime.audit), andverify_trace_claim+ the per-providerverify_*_measurementfunctions (cmcp_verify). It reproduces the gateway's actual nonce construction (JWK thumbprint ‖ salt, perstartup.py) so the verifier's key-binding check passes on hardware.What still needs the vendor services (not just hardware)
P5 verifies format + measurement + nonce binding but not the silicon cert chain. AMD KDS (VCEK/VLEK), Intel DCAP (quote signature/TCB), and TPM EK chain validation appear under
unverified_fieldsuntil wired intocmcp_verify. Documented in the README as the last hardware-dependent step.Docs
experiments/claim-hw-attestation/README.md: hardware options (Azure DCasv5/DCesv6, GCP n2d/c3), the deploy → config → run → verify sequence, samplecmcp-config.yaml, expected output, and the cert-chain caveat.experiments/README.mdindex updated.🤖 Generated with Claude Code