What is NVIDIA Confidential Computing & Attestation?
NVIDIA Confidential Computing (CC) creates a secure, isolated environment directly on the GPU. Think of it as a locked, tamper-proof “black box” where your AI model and data are processed. Nothing outside this box—not even the server’s operating system—can see or interfere with what happens inside. Attestation is the proof that this “black box” is genuine. It’s a digitally signed report from the GPU itself that cryptographically answers two key questions:- “Am I a real NVIDIA GPU?” - It confirms the hardware is authentic and not an emulator.
- “Is my environment secure?” - It verifies that the GPU’s firmware and drivers are up-to-date and haven’t been tampered with.
How APUS Delivers Attestations
You don’t need to do anything extra to enable this powerful security feature. We’ve integrated the NVIDIA Attestation SDK directly into our HyperBEAM service nodes. Every time you make an AI inference request, our service automatically generates a new attestation from the GPU that performed the computation. This attestation is then attached to the response message we send back to your AO process. You’ll find it in theX-Attestation tag.
This means every single AI result you receive comes with a cryptographic proof of its origin and integrity, bringing true on-chain verifiability to AI.
How to Verify an Attestation
The Easy Way (Using the APUS Verifier Service)
For your convenience, we have encapsulated the NVIDIA verification logic into a simple, dedicated service endpoint running on our HyperBEAM node. You can send the attestation data directly to this endpoint and get a simple “pass” or “fail” result. This is the recommended method for most use cases during the Hackathon. Endpoint:http://72.46.85.207:8734/~cc@1.0/verify
How to Use:
Simply make a GET request to the endpoint, passing the full attestation string you received as the request body.
Here is a curl command example. Replace YOUR_ATTESTATION_STRING_HERE with the actual value from the X-Attestation tag.
- Successful Verification: If the attestation is valid, the service will return true.
- Failed Verification: If the attestation is invalid or tampered with, the service will return an error message.
The Advanced Way (Using the NVIDIA SDK)
For developers who require full control over the verification process or wish to integrate it directly into their own trusted backend, you can verify the attestation token using NVIDIA’s official Attestation SDK. This method is more complex as it requires setting up a Python environment and understanding the SDK’s components. Prerequisites:-
Python Environment: You need
Python 3.8or later. -
NVIDIA Attestation SDK: You must install the SDK from PyPI. It’s recommended to do this in a virtual environment.
- Obtain the Attestation Token: This is the full string from the
X-Attestationtag in our service’s response message. - Create a Policy File: This is a JSON file that defines the specific claims you expect to see in a valid token. For example, you can enforce that the GPU driver version is correct or that secure boot is enabled. You can find an example policy file in the SDK documentation.
- Use the SDK to Validate: Write a Python script that uses the
nv_attestation_sdkto validate the token against your policy file.
- NVIDIA Attestation SDK on GitHub: [Link to
nvtrustGitHub repo] - Sample Verification Scripts: Refer to
RemoteGPUTest.pyandLocalGPUTest.pyin the SDK’stestsdirectory.