Fortanix Confidential Computing Manager Architecture (On-premises Only)

1.0 Introduction

Fortanix Confidential Computing Manager (CCM) is a centralized control plane for deploying and managing applications in Trusted Execution Environments (TEEs). CCM enables organizations to protect sensitive applications and data during execution (data-in-use) using platform-based isolation technologies such as Intel® TDX, AMD SEV-SNP, AWS Nitro Enclaves, and Microsoft Azure confidential computing offerings.

Fortanix CCM verifies platform integrity through hardware-based remote attestation and enforces policy-driven release of secrets, certificates, and cryptographic material. Sensitive assets are provisioned to workloads only after successful validation of platform and workload measurements, ensuring that they execute in an approved and trusted environment.

This guide describes the architecture and building blocks of Fortanix CCM On-Premises.

1.1 Overview

Fortanix CCM enables confidential workloads to run in TEEs while ensuring that only verified workloads receive secrets and certificates. The architecture consists of customer-managed infrastructure, CCM services, and external attestation services.

2.0 Architecture

3.0 Components

3.1 Customer Infrastructure

• Confidential Virtual Machine (CVM)/Application: The application workload runs inside a CVM that is protected by a TEE. Depending on the deployment platform, the TEE may be provided by technologies such as Intel TDX, AMD SEV-SNP, NVIDIA Confidential Computing, or AWS Nitro Enclaves. These technologies help protect data while it is being processed and provide attestation evidence that can be verified by Fortanix CCM.

• Node Agent: The Node Agent runs within the customer environment and acts as the communication bridge between the workload and Fortanix CCM. It collects attestation evidence from the platform, submits it to CCM for verification, enrolls infrastructure with CCM, and proxies application certificate requests. The Node Agent enables CCM to verify the trustworthiness of the environment before issuing certificates or releasing sensitive information.

3.2 CCM Services

• CCM Backend: The CCM Backend is the central management component of Fortanix CCM. It manages applications, builds, configurations, clusters, and attestation policies. The service is implemented as a Fortanix EDP application running inside an Intel SGX enclave, providing additional protection for security-sensitive operations such as attestation validation and certificate issuance.

• Database: The database stores application metadata, configuration information, infrastructure enrollment data, and other operational information required by CCM. The datastore is encrypted to help protect the confidentiality and integrity of stored data.

3.3 Remote Attestation Services

Fortanix CCM integrates with platform-specific attestation services to verify the authenticity and integrity of confidential computing environments:

• Microsoft Azure Attestation (MAA) for Azure confidential workloads.

• AMD Key Distribution Service (KDS) for AMD SEV-SNP attestation.

• NVIDIA Remote Attestation Service (NRAS) for NVIDIA confidential computing platforms.

• Provisioning Certificate Caching Service (PCCS) for Intel attestation-related services.

  SERVICE	DEFAULT ENDPOINT	CONFIGURATION
  Microsoft Azure Attestation (MAA)	https://sharedeus.eus.attest.azure.net	Configurable by the System Administrator
  NVIDIA Remote Attestation Service (NRAS)	https://nras.attestation.nvidia.com	Configurable by the System Administrator
  Fortanix PCCS	https://pccs.fortanix.com	Fixed endpoint (not configurable)
  AMD Key Distribution Service (KDS)	https://kdsintf.amd.com/vcek/v1/	Fixed endpoint (not configurable)

3.4 Certificate Issuance and Attestation Flow

The following sequence describes how Fortanix CCM verifies a workload through remote attestation and issues certificates to trusted applications.

1. A confidential workload starts in a CVM.

2. The Node Agent collects attestation evidence from the platform.

3. The Node Agent sends the attestation evidence to Fortanix CCM.

4. Fortanix CCM validates the evidence using the appropriate remote attestation service.

5. After successful verification, Fortanix CCM confirms that the workload is running in a trusted environment.

6. Fortanix CCM issues application certificates and releases any configured secrets.

7. The application uses the issued credentials to securely communicate with other services.