nv-attestation-sdk 2.6.0

The Attestation SDK provides developers with a easy to use APIs for implementing attestation capabilities into their applications.

NVIDIA Attestation SDK

The Attestation SDK offers developers easy-to-use APIs for implementing attestation capabilities into their Python applications. With this SDK, you can seamlessly integrate secure and reliable attestation services into your software, thereby ensuring the authenticity, integrity, and trustworthiness of your system.

• NVIDIA Attestation SDK
  • Features
  • Install Attestation SDK
    • From Source
    • From PyPI
    • Troubleshooting Installation Issues
  • GPU Attestation
    • Pre-requisites
    • How to do Attestation
  • Switch Attestation
    • Pre-requisites
    • How to do Attestation
  • Claims and Troubleshooting information
  • Policy File
  • Building Attestation SDK
  • Compatibility
  • Attestation SDK APIs
  • Attestation SDK configuration
  • Note
  • License
  • Support

Features

• Local GPU Attestation (using NVIDIA NVML based Python libraries)
• Remote GPU Attestation (using NVIDIA Remote Attestation Service)
• Local Switch Attestation (using NVIDIA NSCQ based Python libraries)
• Remote Switch Attestation (using NVIDIA Remote Attestation Service)

Install Attestation SDK

Before installation, please review the Compatibility Matrix to determine the correct version of nvTrust and driver to install.

From Source

Install nv-local-gpu-verifier as a pre-requisite. If you choose to install the Attestation SDK from the source code, use the following commands:

cd attestation_sdk
pip3 install .

From PyPI

If you choose to install the Attestation SDK directly from PyPI, use the following commands (requires virtual environment creation):

python3 -m venv venv
source venv/bin/activate
pip3 install nv-attestation-sdk

Troubleshooting Installation Issues

If you encounter warning and installation issues similar to the below while installing the package: WARNING: Ignoring invalid distribution ~v-attestation-sdk <site-package-directory>

Please execute the following commands to clean up packages that were not installed properly and then re-try the installation:

     rm -rf $(ls -l <site-packages-directory> | grep '~' | awk '{print $9}')

GPU Attestation

Pre-requisites

1. Create a Confidential Virtual Machine with the following specifications:

   • NVIDIA Hopper H100 (or later) GPU that supports CC
   • NVIDIA GPU Driver with CC / PPCIE support.
   • GPU SKU that supports Confidential Computing.

2. Install Python 3.8 or later.

3. Follow the instructions in nvTrust/guest_tools/local_gpu_verifier/README.md to install the NVIDIA GPU Local Verifier Python SDK. (Required for source code installation only)

4. Run the following command and ensure that you have the 'nv-local-gpu-verifier' Python module installed.

   pip list | grep nv-local-gpu-verifier
   nv-local-gpu-verifier  <version>
   

How to do Attestation

• Local GPU Attestation

  Refer to the sample implementation

• Remote GPU Attestation

  Refer to the sample implementation

Switch Attestation

Pre-requisites

1. Create a Confidential Virtual Machine with multiple GPUs connected by nvSwitch with the following specifications:

   • LS10 Switch supporting PPCIE mode
   • NvSwitch Driver with PPCIE support.
   • GPU SKU that supports Confidential Computing.

2. Unlike GPU Verifier, Switch Verifier comes pre-installed with Attestation SDK.

How to do Attestation

• Local nvSwitch Attestation

  Refer to the sample implementation

• Remote nvSwitch Attestation

  Refer to the sample implementation

Claims and Troubleshooting information

For local and remote verifier claims information for NVIDIA GPUs, switches, and related troubleshooting information, please refer to the Attestation Troubleshooting documentation.

Policy File

You can find a sample Attestation Result policy file for Local and Remote Attestation here. Please note that the Schema/EAT claim information is subject to change in future releases.

Building Attestation SDK

python3 -m pip install --upgrade build
python3 -m build

Compatibility

Driver Version

• Use the latest GPU verifier version for optimal compatibility with the most recent drivers.
• For attestation-specific platforms like Blackwell, ensure device-specific CC-enabled drivers are installed (e.g., R575 for Blackwell).

Claims Version

SDK version	Claims Version
v1.1.0	N/A
v1.2.0	N/A
v1.3.0	N/A
v1.4.0	N/A
v1.5.0	N/A
v2.0.0	2.0
v2.1.0	2.0
v2.1.1	2.0
v2.1.2	2.0
v2.1.3	2.0
v2.1.4	2.0
v2.3.0	2.0
v2.4.0	2.0, 3.0
v2.5.0	2.0, 3.0
v2.6.0	2.0, 3.0

More information on claims can be found here

Attestation SDK APIs

nv_attestation_sdk import attestation

API	Description
Attestation(<-name->)	Create a new Attestation Object used to call other Attestation methods.
set_name(<-name->)	Set a name for the Attestation SDK client
set_nonce(<-nonce->)	Set a nonce for Attestation
set_ocsp_nonce_disabled(<-bool->)	Flag which indicates whether to include a nonce when calling OCSP. Only applicable for local GPU attestation. False by default
set_service_key(<-key->)	Service key which is used to auth remote service calls to attestation services. None by default. Note: No valid service keys have been created by admins yet - using any key will result in attestation failure.
set_claims_version(<-version->)	Set a claims version for Attestation. Please refer to the Attestation Troubleshooting documentation for the claims. If claims version is not set, it defaults to 2.0.
add_verifier(<-attestation-device-type->, <-local/remote->, <-remote-attestation-service-url->, <-attestation-results-policy->)	Add a specific type of verifier for the client object. The verifier will be invoked during the attest operation
get_verifiers()	Retrieves the list of verifiers added to the client object.
get_evidence()	Retrieves the list of evidence based on the attestation device (e.g., GPU, switch) and the type of attestation (e.g., local, remote).
attest()	Trigger the Attestation for the client object, This uses the Attestation type configured in the add_verifier method
get_token()	Retrieves the Attestation token that contains claims corresponding to the Attestation result.
get_ocsp_nonce_disabled()	Retrieves the flag which indicates whether a nonce is included when calling OCSP.
get_claims_version()	Retrieves the claims version added to the client object.
validate_token(<-attestation-results-policy->)	Validate the Attestation Claims against a policy
decode_token(<-jwt-token->)	Decodes the JWT token to claims received by the verifier

Attestation SDK configuration

The below configuration can be set using environment variables in the console

Configuration	Values	Explanation
NV_ALLOW_HOLD_CERT	true/false	Enable attestation if the OCSP revocation status of the certificate in the RIM files is 'certificate_hold'. Defaults to false.'

Note

Please note that starting from nvTrust v1.5.0, the NRAS v1 API and Relying Party Policy version 1.0 have been deprecated. Additionally, installation via wheel files will no longer be supported from v1.5.0 onward.

License

This repository is licensed under Apache License v2.0 except where otherwise noted.

Support

For issues or questions, please file a bug. For additional support, contact us at [e-mail]