NVIDIA Remote Attestation Service (NRAS) / NVIDIA attestation SDK: Verifying an NVIDIA GPU attestation report

Impact

Verifying an NVIDIA GPU attestation report by the default path means calling NVIDIA's hosted Remote Attestation Service and fetching Reference Integrity Manifests from NVIDIA infrastructure. That places a live third-party dependency inside the trust decision for every confidential workload you start: if NRAS is unreachable, your orchestration either blocks workload admission or fails open, and most implementations fail open because blocking looks like an outage. There is no CVE here - it is an architectural exposure that operators consistently discover during their first NRAS incident rather than during design.

Who can reach it

Not an attacker in the usual sense. The realistic events are an NRAS outage, a network egress policy that blocks it, or an air-gapped deployment where it was never reachable at all.

What to do

Deploy the local verifier path rather than the remote one where your threat model allows: NVIDIA supports local attestation verification with cached RIMs and the device identity certificate chain, which removes the runtime dependency. Cost: you take on RIM caching and freshness management. Whichever you choose, test the failure mode deliberately - block NRAS in staging and confirm your admission controller denies rather than admits.

References