---
title: Network and Firewall Requirements
slug: kron-pam-installation-guides-v3/network-and-firewall-requirements
createdAt: 2026-11-20T10:19:48.613Z
---

The firewall rules in this section must be configured on the **network-level firewall** protecting the network segment where the related server is deployed (for example: perimeter firewall, DMZ firewall, cloud network firewall). These rules apply to the network firewall in front of the server, not to any host-based firewall running on the server itself.

The WireGuard port **51820** used in the tables below is an example; the port is defined during the installation (**WireGuard VPN port** parameter) and might be changed. The same port must be used on both ends of the tunnel.

:::hint{type="info"}
**RPAM MTC Installer access (TCP 8443)**

During the installation, the administrator's workstation must be able to reach **TCP 8443** (HTTP) on the server where the RPAM MTC Installer runs. If the firewalld service is active on the server, run.sh opens 8443/tcp automatically; the network-level firewall must be configured separately.

The automatic public-key fetch between WireGuard peers also uses this port: the installer requests the key of the peer from **http\://\{real IP of the peer}:8443/api/public-key**, i.e., from the RPAM MTC Installer running on the peer host. For the automatic fetch to work, the installer of the peer must be running, the peer must have completed its own installation, and TCP 8443 of the peer must be reachable (RPAM Connector / Kron PAM Server → RPAM Portal, and RPAM Portal → RPAM Connector). Otherwise, the public key can be entered manually (see Section 9).
:::

:::Heading{depth="2" indent="1"}
RPAM With RPAM Connector
:::

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>RPAM Portal</u>

1\) HTTPS Access to the RPAM Portal (TCP): Allow external users to access the RPAM Portal web interface.

2\) WireGuard Tunnel Traffic (UDP): The WireGuard tunnel is established between the RPAM Connector (client) and the RPAM Portal (server).

**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**                | **Destination** | **Protocol** | **Port**                 |
| ------------- | ------------------------- | --------------- | ------------ | ------------------------ |
| Inbound       | Internet / External Users | RPAM Portal     | TCP          | 443                      |
| Inbound       | RPAM Connector            | RPAM Portal     | UDP          | 51820 (might be changed) |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**                | **Destination** | **Protocol** | **Port**                 |
| ------------- | ------------------------- | --------------- | ------------ | ------------------------ |
| Inbound       | Internet / External Users | RPAM Portal     | TCP          | 443                      |
| Inbound       | RPAM Connector            | RPAM Portal     | UDP          | 51820 (might be changed) |
| Outbound      | RPAM Portal               | RPAM Connector  | UDP          | 51820 (might be changed) |

<u>**Note:**</u>

Port 7777 is strictly internal to the RPAM Portal server and must never be exposed on the network firewall.

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>RPAM Connector</u>

1\) WireGuard Tunnel Traffic (UDP): Allow the RPAM Connector to initiate the WireGuard tunnel to the RPAM Portal.

2\) Forwarded Traffic to the Kron PAM Server: Allow the HTTPS traffic forwarded by the RPAM Connector to reach the Kron PAM Server.



**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**     | **Destination** | **Protocol** | **Port**                 |
| ------------- | -------------- | --------------- | ------------ | ------------------------ |
| Outbound      | RPAM Connector | RPAM Portal     | UDP          | 51820 (might be changed) |
| Outbound      | RPAM Connector | Kron PAM Server | TCP          | 443                      |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**     | **Destination** | **Protocol** | **Port**                 |
| ------------- | -------------- | --------------- | ------------ | ------------------------ |
| Outbound      | RPAM Connector | RPAM Portal     | UDP          | 51820 (might be changed) |
| Inbound       | RPAM Portal    | RPAM Connector  | UDP          | 51820 (might be changed) |
| Outbound      | RPAM Connector | Kron PAM Server | TCP          | 443                      |

:::Heading{depth="2" indent="1"}
RPAM Without RPAM Connector (On-PAM)
:::

The rules for the network firewall protecting the **RPAM Portal** are the same as in Section 3.1; only the **RPAM Connector** is replaced with the **Kron PAM Server** as the WireGuard peer.

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>Kron PAM Server</u>

1\) HTTPS Traffic from the RPAM Portal to the Kron PAM Server (TCP): Allow the Kron PAM Server to receive HTTPS traffic from the RPAM Portal over the WireGuard tunnel.

2\) WireGuard Tunnel Traffic (UDP): Allow the Kron PAM Server to communicate with the RPAM Portal over WireGuard.

**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**      | **Destination** | **Protocol** | **Port**                 |
| ------------- | --------------- | --------------- | ------------ | ------------------------ |
| Outbound      | Kron PAM Server | RPAM Portal     | UDP          | 51820 (might be changed) |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**      | **Destination** | **Protocol** | **Port**                 |
| ------------- | --------------- | --------------- | ------------ | ------------------------ |
| Outbound      | Kron PAM Server | RPAM Portal     | UDP          | 51820 (might be changed) |
| Inbound       | RPAM Portal     | Kron PAM Server | UDP          | 51820 (might be changed) |

:::Heading{depth="2" indent="1"}
MTC Outbound Built-in VPN
:::

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>Kron PAM Server</u>

**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**      | **Destination**        | **Protocol** | **Port**                                          |
| ------------- | --------------- | ---------------------- | ------------ | ------------------------------------------------- |
| Inbound       | Internet Users  | Kron PAM Server        | TCP          | 443                                               |
| Outbound      | Kron PAM Server | Multi Tenant Connector | TCP          | 22 (initial setup only; can be closed afterwards) |
| Outbound      | Kron PAM Server | Multi Tenant Connector | UDP          | 10000 (might be changed)                          |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**             | **Destination**        | **Protocol** | **Port**                                          |
| ------------- | ---------------------- | ---------------------- | ------------ | ------------------------------------------------- |
| Inbound       | Internet Users         | Kron PAM Server        | TCP          | 443                                               |
| Inbound       | Multi Tenant Connector | Kron PAM Server        | UDP          | 10000 (might be changed)                          |
| Inbound       | Multi Tenant Connector | Kron PAM Server        | TCP          | Ephemeral (1024–65535) – for 22                   |
| Outbound      | Kron PAM Server        | Multi Tenant Connector | TCP          | 22 (initial setup only; can be closed afterwards) |
| Outbound      | Kron PAM Server        | Multi Tenant Connector | UDP          | 10000 (might be changed)                          |

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>Multi Tenant Connector</u>

**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**             | **Destination**        | **Protocol** | **Port**                              |
| ------------- | ---------------------- | ---------------------- | ------------ | ------------------------------------- |
| Inbound       | Kron PAM Server        | Multi Tenant Connector | UDP          | 10000 (might be changed)              |
| Outbound      | Multi Tenant Connector | Target Devices         | TCP          | Service Ports (SSH:22, RDP:3389 etc.) |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**             | **Destination**        | **Protocol** | **Port**                              |
| ------------- | ---------------------- | ---------------------- | ------------ | ------------------------------------- |
| Inbound       | Kron PAM Server        | Multi Tenant Connector | UDP          | 10000 (might be changed)              |
| Inbound       | Target Devices         | Multi Tenant Connector | TCP          | Ephemeral (1024–65535)                |
| Outbound      | Multi Tenant Connector | Kron PAM Server        | UDP          | 10000 (might be changed)              |
| Outbound      | Multi Tenant Connector | Target Devices         | TCP          | Service Ports (SSH:22, RDP:3389 etc.) |

<u>**Note:**</u>

For the device mapping between the Kron PAM Server and the Multi Tenant Connector, the **predefined TCP ports** (starting with 40000) are used. Each device assigned to the Multi Tenant Connector on the Device page of the Kron PAM Web GUI has an internal port that the connector routes with iptables toward the real connection port. That is, when a request to access port 40000 comes to the Multi Tenant Connector from the Kron PAM Server, the Multi Tenant Connector forwards the request to the IP address and the real connection port (e.g., 22 or 3389) of the device by port forwarding with iptables. <u>**These TCP ports (starting with 40000) are internal mapping constructs and do not require firewall allowance.**</u>

:::Heading{depth="2" indent="1"}
MTC Inbound Built-in VPN
:::

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>Kron PAM Server</u>

**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**             | **Destination** | **Protocol** | **Port**                 |
| ------------- | ---------------------- | --------------- | ------------ | ------------------------ |
| Inbound       | Internet Users         | Kron PAM Server | TCP          | 443                      |
| Inbound       | Multi Tenant Connector | Kron PAM Server | UDP          | 10000 (might be changed) |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**             | **Destination**        | **Protocol** | **Port**                 |
| ------------- | ---------------------- | ---------------------- | ------------ | ------------------------ |
| Inbound       | Internet Users         | Kron PAM Server        | TCP          | 443                      |
| Inbound       | Multi Tenant Connector | Kron PAM Server        | UDP          | 10000 (might be changed) |
| Outbound      | Kron PAM Server        | Multi Tenant Connector | UDP          | 10000 (might be changed) |

### Prerequisites: Required Firewall Rules on the Network Firewall Protecting the <u>Multi Tenant Connector</u>

**Stateful Network Firewall (Recommended and Most Common)**

Stateful firewall examples include enterprise and cloud firewalls such as Palo Alto Networks, FortiGate, Check Point, Cisco ASA/FTD, Juniper SRX, and AWS Security Groups.

<u>**Required Rule:**</u>

| **Direction** | **Source**             | **Destination** | **Protocol** | **Port**                              |
| ------------- | ---------------------- | --------------- | ------------ | ------------------------------------- |
| Outbound      | Multi Tenant Connector | Kron PAM Server | UDP          | 10000 (might be changed)              |
| Outbound      | Multi Tenant Connector | Target Devices  | TCP          | Service Ports (SSH:22, RDP:3389 etc.) |

**Stateless Network Firewall**

In stateless firewall environments, traffic is evaluated per packet and connection state is not tracked.

<u>**Required Rules:**</u>

| **Direction** | **Source**             | **Destination**        | **Protocol** | **Port**                              |
| ------------- | ---------------------- | ---------------------- | ------------ | ------------------------------------- |
| Inbound       | Kron PAM Server        | Multi Tenant Connector | UDP          | 10000 (might be changed)              |
| Inbound       | Target Devices         | Multi Tenant Connector | TCP          | Ephemeral (1024–65535)                |
| Outbound      | Multi Tenant Connector | Kron PAM Server        | UDP          | 10000 (might be changed)              |
| Outbound      | Multi Tenant Connector | Target Devices         | TCP          | Service Ports (SSH:22, RDP:3389 etc.) |

<u>**Note:**</u>

For the device mapping between the Kron PAM Server and the Multi Tenant Connector, the **predefined TCP ports** (starting with 40000) are used. Each device assigned to the Multi Tenant Connector on the Device page of the Kron PAM Web GUI has an internal port that the connector routes with iptables toward the real connection port. That is, when a request to access port 40000 comes to the Multi Tenant Connector from the Kron PAM Server, the Multi Tenant Connector forwards the request to the IP address and the real connection port (e.g., 22 or 3389) of the device by port forwarding with iptables. <u>**These TCP ports (starting with 40000) are internal mapping constructs and do not require firewall allowance.**</u>
