Remote attestation

Verify the workload before trusting the connection.

Canopy's secure-route protocol can combine Intel SGX DCAP evidence, application identity policy, fresh key agreement, and protected RPC in one session. The implementation has demonstrated a three-enclave hardware route. Customer deployments package that capability with the trust policy, credentials, collateral, trusted time, and qualification for their target hardware.

Canopy is designed to be attestation-backend agnostic. Its common evidence, claims, policy, and secure-session model provides the path to heterogeneous bilateral attestation: each endpoint can use a different evidence technology while sharing the same transcript-bound protected route.

Compare protection tiers View the DCAP trace

What Canopy can do now

Mutual or one-sided attestation

A route can require peer evidence, present local evidence, or require both endpoints to attest before the secure session becomes active.

Bind evidence to the live session

Fresh nonces, endpoint identities, credentials, policy profiles, verifier challenges and both ephemeral key shares are covered by the attested transcript.

Apply workload and TCB policy

DCAP appraisal can enforce enclave and signer measurements, Product ID, minimum security version, debug state, collateral status and accepted TCB results.

Protect RPC end to end

Accepted evidence feeds the same X25519 key agreement and AES-256-GCM protected-RPC layer used across direct and multi-hop Canopy routes.

Intel SGX DCAP

Canopy includes quote generation, host QvL verification, enclave-side QvE/TVL verification, normalized claims, trusted-time integration points and fail-closed policy. Fake and SGX-simulation backends are also available for integration and CI testing without presenting themselves as hardware evidence.

Secure-route capability Transcript-bound evidence, mutual secure-route handshakes, protected RPC, replay protection, policy-controlled claims, expiring sessions and background re-attestation and rekey.
Hardware demonstrated Three independently loaded Release enclaves established protected routes through an intermediate enclave, completed a 100-sample RPC benchmark, and rejected a deliberately wrong signer.
Customer deployment Each production profile freezes and qualifies the accepted TCB state, hardware fault tests, workload identity, credentials, trusted-time authorities, and trust policy for the customer's environment.

Browser and external-client attestation

Canopy also provides a protected-session profile for browser JavaScript, Node.js and native clients. It binds the client nonce, selected interface fingerprints, origin or carrier context, effective configuration, workload identity and fresh session keys to the evidence before application RPC begins.

The JavaScript client includes local appraisal for integration testing and a Microsoft Azure Attestation adapter that validates DCAP binding and signed MAA results against independently supplied trust keys and application policy. Customer delivery packages the browser assets, independently trusted keys, key lifecycle, application policy, and target-hardware appraisal as one reviewed profile.

Deployment model and optional expansion

Customer-qualified SGX A production engagement packages current-TCB hardware qualification, trusted-time authorities, identity policy, route credentials, collateral handling, and operational rotation around the implemented DCAP route.
More confidential-computing platforms Beyond SGX, the roadmap tracks AMD SEV-SNP, Arm CCA and Arm PSA. Intel TDX, AWS Nitro, TPM/DICE and confidential-GPU evidence are deployment-led future backends.
Heterogeneous bilateral attestation The backend-neutral bilateral model is designed for each endpoint to present a different evidence profile — for example SGX on one side and SEV-SNP or CCA on the other — while sharing the same transcript binding, normalized policy decision, and protected-RPC channel.
External-client delivery Browser packaging and the authenticated MAA trust-key lifecycle are configured with the customer profile. Optional cross-zone relay and a future WebTransport profile build on the existing protected external session.
Cryptographic agility A future secure-session version will support reviewed suite migration, including evaluation of hybrid X25519 plus ML-KEM key establishment without downgrade.

Attestation is part of the trust decision

Platform evidence proves the properties selected by policy. Canopy then binds that verdict to the live encrypted route; application authentication and object-level authorization remain explicit controls rather than assumptions hidden inside a quote.

See product applications