Security#
Notes#
NVIDIA provides a reference architecture for Audio2Face-3D(A2F-3D) Authoring 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 Authoring service is running
Audio toxicity checks are not provided
Logging & Auditing#
Audio2Face-3D Authoring 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 Authoring service are responsible for logging and auditing
AI models#
The AI models come as part of the Audio2Face-3D Authoring container
The AI models are not encrypted
Encryption#
Audio2Face-3D Authoring service doesn’t provide encryption support
Audio2Face-3D Authoring service doesn’t store any keys
Data collection#
Audio2Face-3D Authoring services don’t collect any sensitive information including any private user data
Input Audio data is cached for a certain duration(configurable) in a in-memory database.