Networking Requirements

Prev Next

Fortanix Armor requires network connectivity to access external repositories and services and to support communication with the Kubernetes cluster during deployment. Ensure that the following network destinations are whitelisted to allow the required connections. For detailed traffic flow, refer to the Fortanix Armor Architecture Diagram (on-premises).

PROTOCOL

INBOUND / OUTBOUND

PORT NUMBER

PURPOSE

TCP

Inbound

443

HTTPS - Used for static content

TCP

Inbound

443

HTTPS - Used for Web UI and API access

TCP

Outbound

443

Internet - Azure Attestation service

TCP

Outbound

443

Azure’s Provisioning Certificate Caching Service (PCCS) endpoint (global.acccache.azure.net)

TCP

Outbound

443

Fortanix PCCS endpoint (pccs.fortanix.com)

TCP

Outbound

443

Intel Trust Authority (api.trustedservices.intel.com) for remote attestation

TCP

Outbound

443

Fortanix OCI registry (cr.download.fortanix.com) for Fortanix Armor container images and Helm charts

TCP

Outbound

443

Azure Blob Storage (*.blob.core.windows.net) for Armor platform backup

TCP

Outbound (Optional)

514

External Syslog server for audit logging, if configured

Fortanix-logo

4.6

star-ratings

As of August 2025