Fortanix Integrates Attestation and Key Management with Kubernetes Confidential Containers
Fortanix enables secure workload decryption by linking Kubernetes attestation to hardware-based trusted execution environments.
1Confidential Containers Architecture
Confidential Containers, a Cloud Native Computing Foundation project, execute Kubernetes pods within confidential virtual machines. Unlike standard containers relying on host OS isolation, these VMs utilize hardware-based trusted execution environments to encrypt memory. This approach secures data during active processing, enabling sensitive workloads to operate safely on shared infrastructure environments.
2Fortanix Integration Mechanism
Fortanix integrates its Confidential Computing Manager and Data Security Manager with Confidential Containers to automate trust. The Confidential Computing Manager verifies the environment, while the Data Security Manager releases encryption keys only upon successful verification. This workflow ensures that workloads can only decrypt models if they meet established security policies.
3Hardware Evidence Validation
The integration supports attestation for both processors and GPUs, depending on specific configuration settings. Fortanix deployment guides for Intel TDX allow users to mandate GPU validation through NVIDIA services or ignore the result. This process ensures that hardware evidence is collected and verified before any sensitive secrets are released to containers.
4Trustee and Open Source
The open-source Trustee project already provides similar attestation and conditional secret delivery capabilities. It separates evidence appraisal from resource authorization, using a Key Broker Service to apply user-defined policies. Fortanix is currently developing additional open-source plugins for Confidential Containers, building upon the existing framework to enhance standard workload security adoption.
5Deployment and Operational Requirements
Fortanix offers its management services as a hosted solution, on-premises, or in air-gapped environments with 24x7 support. Deployment requires installing the Fortanix Helm chart, though users must manually configure host firmware and kernel settings beforehand. The September 17 release notes confirm support for AMD SEV-SNP and Intel TDX environments.
6Trust Boundary Limitations
The security model requires teams to trust the guest kernel and helper processes residing within the trust boundary. Hardware measurements cover the guest environment, but container verification remains a distinct stage. Furthermore, the model excludes denial-of-service protection and hardware side channels, noting that attestation does not guarantee safe data handling.
7Alternative Managed Solutions
Microsoft provides an alternative through Azure Secure Key Release, integrated with Azure Attestation within Key Vault Premium and Managed HSM. Unlike the Fortanix approach, this service specifically releases exportable keys rather than secrets or certificates. These managed options offer different paths for teams seeking to implement confidential computing within cloud environments.
8Strategic Security Impact
By combining attestation and key management into a single platform, Fortanix allows organizations to adopt Confidential Containers without building complex custom trust layers. This integration addresses the critical need to protect data in use, moving beyond traditional encryption at rest or in transit to secure sensitive AI model execution.