This article provides an overview of new features and improvements in the Fortanix Confidential Computing Manager (CCM) 4.9 release.
1. New Features
Fortanix CCM Support for On-Premises Deployments:
Fortanix CCM is now available for on-premises deployments, enabling customers to run CCM within their own infrastructure.
For detailed Fortanix CCM installation instructions, refer to Installation Guide - On-premises.
For a list of features supported in Fortanix CCM on-premises deployments, refer to Feature Support Matrix - SaaS vs On-premises.
NOTE
Support for Azure Kubernetes Service (AKS) is currently validated only on development-grade AKS clusters. Support for Production AKS clusters will be validated and any issues addressed in a future patch release.
2. Improvements
Added support for verifying that the virtual Trusted Platform Module (vTPM) Attestation Key public key (AkPub) matches the value in the Microsoft Azure Attestation (MAA) JSON Web Token (JWT) in the Azure Confidential Virtual Machine (CVM) Windows and Linux Azure Confidential Virtual Machine (CVM) attestation client.
3. Security Fixes
Fixed an issue where certain validation checks for enclave build artifacts were not consistently executed.
4. Known Issues
In Fortanix CCM on-premises deployments, user profile deletion may fail in certain scenarios due to unresolved account dependencies, even after the associated account appears to have been deleted.
5. Installation
For the corresponding version of the Fortanix Armor Kubernetes Operator Helm Chart, click here.
Download the latest Fortanix Node Agent Software - SGX from here.
Download the latest Fortanix Azure CVM Attestation Client - Linux (Ubuntu 24.04) from here.
Download the latest Fortanix Azure CVM Attestation Client - Windows (Windows Server 2025) from here.
6. Limitations
Fortanix has a fair usage policy in this Early Customer Access Program. Hence, Fortanix has limited the resources one can create per account. Therefore, it is expected to observe a resource creation failure message once you have reached the maximum limit.
To report an issue or bug, visit New Requests.