Server components

Recommended software and Hardware requirements are provided for each component. To calculate an individual PAM configuration, contact technical support.

Management Server

Note

The system requirements were determined during tests in a test environment with a typical load profile.

Windows

Hardware requirements
Parameters	50 sessions	100 sessions	200 sessions
CPU RAM HDD/SSD Network adapter	8 cores 8 GB 120 GB 1 Gbps	16 cores 16 GB 120 GB 1 Gbps	32 cores 32 GB 120 GB 1 Gbps
Operating system	Windows Server 2016–2022
Domain	Microsoft Active Directory
Web Server	Internet Information Services 8.5–10.0
Modules for the IIS Web server	Basic Authentication Windows Authentication Static Content HTTP Redirection ASP.NET Core Runtime ISAPI Extensions .NET Extensibility ISAPI Filters IIS Management Console
Additional Microsoft components	Microsoft .NET Core 8 URL Rewrite

Network Connectivity

Incoming

Protocol	Port	Description
TCP	443	User console, API, IdP connection Management Server health monitoring

Outgoing

Protocol	Port	Description
TCP	389, 636	Directory Service Reading
TCP	389, 636	Service operations in Directory Service
TCP	5985, 5986	Service operations on Windows resources over HTTP and HTTPS by using the WinRM service
TCP	445	Verifying and changing local account passwords on Windows resources
TCP	22	Service operations on Linux and Cisco IOS XE resources, and on Inspur BMC
TCP	1433	Service operations or data recording in Microsoft SQL Server database
TCP	5432	Service operations or data recording in PostgreSQL database
TCP	1521	Service operations in OracleDB database
TCP	3306	Service operations in MySQL database
TCP	445	Recording screenshots to media storage (SMB storage)
TCP	5443	Reading a session stream from the RDS Access Server Gateway Service health monitoring on the RDS Access Server
TCP	8443	Reading a session stream from the RDP Access Server Gateway Service health monitoring on the RDP and SSH Access Servers
TCP	53389	RDP Access Server health monitoring
TCP	52222	SSH Access Server health monitoring
TCP	55432	PostgreSQL Access Server health monitoring
TCP	51433	MSSQL Access Server health monitoring
TCP	58080	Web Access Server health monitoring
TCP	58090	Web Terminal health monitoring

Linux

Hardware requirements
Parameters	50 sessions	100 sessions	200 sessions
CPU RAM HDD/SSD Network adapter	2 cores 4 GB 120 GB 1 Gbps	2 cores 4 GB 120 GB 1 Gbps	2 cores 4 GB 120 GB 1 Gbps
Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)
Disk partitioning	Root file system (/) — partition with application and operating system files. It is recommended to allocate 10–20 GB depending on the installed software. /home — partition for storing user data. Also used for storing temporary files and docker images during PAM installation. At least 10 GB of free space must be allocated. /var — partition for storing temporary files, logs, databases, caches. It is recommended to allocate 20 GB or more. /tmp — partition with temporary files. The partition size should be sufficient for temporary operations, such as unpacking files or storing caches. It is recommended to allocate 10 GB or more. /boot — partition containing the bootloader and kernel. It is recommended to allocate 1 GB taking into account future expansions and updates. swap — partition used as virtual memory. It is recommended to allocate a size equal to the RAM size. /var/lib/docker — partition for Docker root directory, containing docker images, volumes and temporary files. As the number of user sessions increases, the partition size needs to be increased. It is recommended to allocate 100 GB or more. /etc/axidian — partition for PAM data: configurations, certificates, keys, logs. Temporary data awaiting transfer to remote media storage is saved to the partition. It is recommended to allocate 40 GB or more. Disk partitioning example 120 GB Example of partitioning for a server with a disk volume of 120 GB and 16 GB of RAM. Partition Disk volume, GB % of total disk Root file system (/) 10 8,33 /home 10 8,33 /var 20 16,68 /tmp 10 8,33 /boot 1 0,83 swap 16 13,33 /var/lib/docker 38 31,67 /etc/axidian 15 12,50 Note: The /var/lib/docker and /etc/axidian partitions are smaller than the recommended sizes. This layout is suitable only if you use remote media storage and have a typical load profile. As the number of sessions grows, expand the disk and these partitions. 240 GB Example of partitioning for a server with a disk volume of 240 GB and 32 GB of RAM. Partition Disk volume, GB % of total disk Root file system (/) 20 8,33 /home 10 4,17 /var 20 8,33 /tmp 10 4,17 /boot 1 0,42 swap 32 13,33 /var/lib/docker 100 41,67 /etc/axidian 47 19,58

Network Connectivity

Incoming

Protocol	Port	Description
TCP	443	User console, API, IdP connections Management Server health monitoring

Outgoing

Protocol	Port	Description
TCP	389, 636	Directory Service Reading
TCP	389, 636	Service operations in Directory Service
TCP	5985, 5986	Service operations on Windows resources over HTTP and HTTPS by using the WinRM service
TCP	22	Service operations on Linux and Cisco IOS XE resources, and on Inspur BMC
TCP	1433	Service operations or data recording in Microsoft SQL Server
TCP	5432	Service operations or data recording in PostgreSQL
TCP	1521	Service operations in OracleDB
TCP	3306	Service operations in MySQL
TCP	445	Recording screenshots to media storage (SMB storage)
TCP	5443	Reading a session stream from the RDS Access Server Gateway Service health monitoring on the RDS Access Server
TCP	8443	Reading a session stream from the RDP Access Server Gateway Service health monitoring on the RDP and SSH Access Servers
TCP	53389	RDP Access Server health monitoring
TCP	52222	SSH Access Server health monitoring
TCP	55432	PostgreSQL Access Server health monitoring
TCP	51433	MSSQL Access Server health monitoring
TCP	58080	Web Access Server health monitoring
TCP	58090	Web Terminal health monitoring
TCP, UDP	88	User authentication via Kerberos when signing in to PAM (obtaining a ticket from the domain controller, KDC)

RDS Access Server

Note

The system requirements were determined during tests in a test environment with a typical load profile.

Hardware requirements
Parameters	10 RDP or SSH sessions	50 RDP or SSH sessions	100 RDP or SSH sessions
CPU RAM HDD/SSD Network adapter	8 cores 12 GB 160 GB + 5 GB per Axidian Privilege User 1 Gbps	16 cores 32 GB 320 GB + 5 GB per Axidian Privilege User 1 Gbps	32 cores 64 GB 520 GB + 5 GB per Axidian Privilege User 1 Gbps
Operating system	Windows Server 2016–2022
Domain	Microsoft Active Directory
Roles	Remote Desktop Connection Broker (RDCB) Remote Desktop Services Host (RDSH) Remote Desktop Web Access (RDWA)
Additional Microsoft components	Microsoft .NET Desktop Runtime x64 v8 Microsoft Visual C++ 2015–2019 Redistributable
Browser	Google Chrome Microsoft EDGE
Other requirements	Support for Simultaneous MultiThreading (AMD) or Hyper-Threading (Intel) Monitor width resolution of at least 1280 pixels

Network Connectivity

Incoming

Protocol	Port	Description
TCP	3389	Connection to the RDS Access Server
TCP	5443	Reading a session stream Gateway Service health monitoring

Outgoing

Protocol	Port	Description
TCP	443	Interaction with the Management server Note: In a fault-tolerant setup, interaction with the Management server is performed through a load balancer
TCP	3389	Connection to a resource via RDP protocol
TCP	22	Connection to a resource via SSH protocol
TCP	23	Connection to a resource via Telnet protocol
TCP	445	Recording videos of sessions in media storage

RDP Access Server

info

The system requirements were determined during tests in a test environment with a typical load profile.

Hardware requirements
Parameters	10 RDP sessions	50 RDP sessions	100 RDP sessions
CPU RAM HDD/SSD Network adapter	2 cores 4 GB 120 GB 1 Gbps	8 cores 12 GB 120 GB 1 Gbps	8 cores 12 GB 120 GB 1 Gbps
Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)
Other requirements	Monitor width resolution of at least 1280 pixels

Network Connectivity

Incoming

Protocol	Port	Description
TCP	3390	Connection to the RDP Access Server
TCP	8443	Reading a session stream Gateway Service health monitoring
TCP	53389	RDP Access Server health monitoring

Outgoing

Protocol	Port	Description
TCP	443	Interaction with the Management server Note: In a fault-tolerant setup, interaction with the Management server is performed through a load balancer
TCP	3389	Connection to a resource via RDP protocol
TCP	445	Recording videos of sessions in media storage
TCP, UDP	88	Kerberos authentication when connecting to a resource via RDP Proxy (obtaining a ticket from the domain controller, KDC)

SSH Access Server

Note

The system requirements were determined during tests in a test environment with a typical load profile.

Hardware requirements
Parameters	50 SSH sessions	100 SSH sessions	200 SSH sessions
CPU RAM HDD/SSD Network adapter	2 cores 2 GB 120 GB 1 Gbps	2 cores 4 GB 120 GB 1 Gbps	4 cores 4 GB 120 GB 1 Gbps
Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)

Network Connectivity

Incoming

Protocol	Port	Description
TCP	2222	Connection to the SSH Access Server
TCP	52222	SSH Access Server health monitoring
TCP	8443	Gateway Service health monitoring

Outgoing

Protocol	Port	Description
TCP	443	Interaction with the Management server Note: In a fault-tolerant setup, interaction with the Management server is performed through a load balancer
TCP	22	Connection to a resource via SSH/SCP/SFTP protocol
TCP	445	Saving transferred files

PostgreSQL Access Server

Note

The system requirements were determined during tests in a test environment with a typical load profile.

Hardware requirements
Parameters	50 SQL sessions	100 SQL sessions	200 SQL sessions
CPU RAM HDD/SSD Network adapter	2 cores 4 GB 120 GB 1 Gbps	2 cores 4 GB 120 GB 1 Gbps	2 cores 4 GB 120 GB 1 Gbps
Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)

Network Connectivity

Incoming

Protocol	Port	Description
TCP	5432	Connection to the PostgreSQL Access Server
TCP	55432	PostgreSQL Access Server health monitoring

Outgoing

Protocol	Port	Description
TCP	443	Interaction with the Management server Note: In a fault-tolerant setup, interaction with the Management server is performed through a load balancer
TCP	5432	Writing data to the PostgreSQL DBMS

MSSQL Access Server

Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)

Network Connectivity

Incoming

Protocol	Port	Description
TCP	1433	Connection to the MSSQL Access Server
TCP	51433	MSSQL Access Server health monitoring

Outgoing

Protocol	Port	Description
TCP	443	Interaction with the Management server Note: In a fault-tolerant setup, interaction with the Management server is performed through a load balancer
TCP	1433	Writing data to the MSSQL DBMS

Web Terminal Server

Note

The system requirements were determined during tests in a test environment with load distribution:

• 40% on SSH session
• 60% on RDP session

Hardware requirements
Parameters	25 sessions	50 sessions	75 sessions	100 sessions
CPU RAM HDD/SSD Network adapter	single-core 2 GB 120 GB 1 Gbps	2 cores 4 GB 120 GB 1 Gbps	3 cores 6 GB 120 GB 1 Gbps	4 cores 8 GB 120 GB 1 Gbps
Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)

Network Connectivity

Incoming

Protocol	Port	Description
HTTPS	443	Connection to the Web Terminal
TCP	58090	Web Terminal health monitoring

Outgoing

Protocol	Port	Description
TCP	2222	Connection to a resource via SSH Proxy protocol Interaction with the SSH Proxy through a load balancer
TCP	3389	Connection to a resource via RDP Proxy protocol
TCP	3390	Interaction with the RDP Proxy through a load balancer

Web Access Server

Note

The system requirements were determined during tests in a test environment with a typical load profile and based on the recommended scaling for the Video Resolution. Configure this setting before opening a web session.

Hardware requirements
Parameters	10 Web sessions	50 Web sessions	100 Web sessions
CPU RAM HDD/SSD Network adapter	2 cores 6 GB 120 GB 1 Gbps	8 cores 18 GB 120 GB 1 Gbps	16 cores 32 GB 120 GB 1 Gbps
Operating system	Debian 11 and higher Ubuntu 22.04 and higher
Container engine	Docker 18.09 and higher Docker Compose 1.29.2 and higher Note: Docker must be installed from the Linux distribution's repository.
Additional components	iptables 1.4 and higher python 3.8 and higher openssh-server (the version depends on the Linux distribution)

Network Connectivity

Incoming

Protocol	Port	Description
TCP	5443	Connection to the Web Access Server
TCP	58080	Web Access Server health monitoring

Outgoing

Protocol	Port	Description
TCP	443	Connection to a web resource via the HTTPS protocol
TCP	80	Connection to a web resource via the HTTP protocol

CIS Benchmark Security Settings

PAM servers must have CIS Benchmark security settings applied.