Zero-Trust Attestation

NEAR AI

8/10 hardware + TCB0 verified8 incomplete1 failed1 not current

End-to-end verification requires every required evidence gate to be verified. Incomplete evidence means no required gate explicitly failed, but at least one was not proven, was not evaluated, or was excluded as not applicable. It does not imply that hardware verification passed.

Last checked: Oct 27, 2026, 11:01:46 UTC

Latest attempt complete; discovery complete; 10/10 targets completed; 51 excluded (48 × catalog model is not in the provider's confidential/TEE class; 3 × unsupported utility/modality or non-confidential model class)

Summary

Explicit trust failuresAt least one check has an explicit mismatch or policy rejection; other evidence layers may still have passed.

Hardware2 warningTCB policy2 warningFreshness2 warningChannel binding2 warningWorkload identity5 warningSource provenance10 warningRequest route10 warningAvailability1 warning

Verifier policy failed1Source provenance not proven9Request route not proven9Workload identity not proven4

◐DeepSeek V3.2 (TEE)Intel TDXAttested E2EE

Workload identity not provenNo expected workload measurement was verified.

✗GLM 5.3 (TEE)

Verifier policy failedNonce mismatch (possible replay): expected bf2ab77bd6c0d92bba59b1887d455a8487c78d2edb4e9e8bec5cf9e71dd5c251, got missing NEAR AI response nonce

◐GLM 5.3 Flash (TEE)Intel TDXAttested E2EE

Source provenance not provenRegistry existence alone is not source provenance.

⚠Kimi K2.6 (TEE)

Endpoint unavailableFresh evidence could not be fetched in this run.

◐Kimi K3 (TEE)Intel TDXAttested E2EE

Workload identity not provenNo expected workload measurement was verified.

◐Privacy Filter (TEE)Intel TDXAttested E2EE