Port requirements for cluster communication - Add the required ports when installing Cortex XSOAR On-prem. - FAQs - 8 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR 8 - FAQs

Product
Cortex XSOAR
Version
8
Creation date
2023-11-02
Last date published
2025-10-08
Category
FAQs
Abstract

Add the required ports when installing Cortex XSOAR On-prem.

The following ports are required for standalone (one VM) and a three-node cluster (three VMs).

Port

Protocol

Purpose

22

TCP

SSH communication

8880

TCP

Node communication

2049

TCP

Backup and restore server communication

111

TCP

Backup and restore server communication

Required control plane ports

A Kubernetes cluster consists of a control plane and one or more worker nodes. For Cortex XSOAR, in standalone (one VM), the VM acts as both control plane and as a worker node. In multi-node clusters, the first three nodes act as both control plane and as worker nodes, and any additional node added acts as a worker node.

The following ports are required for a control plane.

Name

Port

Protocol

etcd client port

2379

TCP

etcd peer port

2380

TCP

Kubernetes API

6443

TCP

Kubelet API

10250

TCP

kube-scheduler

10257

TCP

kube-controller-manager

10259

TCP

Required worker node port

The following port is required for a worker node.

Name

Port

Protocol

kube nodeport range

30000:32767

TCP

Intra-node communication

The following port is required for a multi-node cluster (three VMs).

Name

Port

Protocol

Calico with IPv4 Wireguard

51820

UDP