Security#
Notes#
NVIDIA provides a reference architecture for Audio2Face-3D (A2F-3D) service, securely develops SW and publishes the containers securely. For production environments the end user is responsible for deploying, defining their trust boundaries, securing their deployments (logging, monitoring, patching, Authorization & Authentication, granular access control, securing communication channels, ensuring containers are secure and free from vulnerabilities..)
Input#
Input data file (Audio) may originate from outside the device where the A2F-3D service is running
Audio toxicity checks are not provided
Logging & Auditing#
Audio2Face-3D service doesn’t provide auditing capabilities. Although basic logging is provided, it is within the scope of the “Device Trust Boundary” and the service logs are limited to the container/device. Applications/Workflows that make use of the Audio2Face-3D service are responsible for logging and auditing
AI models#
The AI models come as part of the Audio2Face-3D container. In case of Audio2Face-3D NIM, models can be downloaded from NGC quick start
The AI models are not encrypted
Encryption#
Audio2Face-3D service doesn’t provide encryption support
Audio2Face-3D service doesn’t store any keys
Data collection#
Audio2Face-3D services don’t collect any sensitive information including any private user data
Input Audio data is processed to generate blendshapes and the audio is not stored