Inbound and Outbound Ports
As a network application, Tenable Patch Management requires specific ports to facilitate communication between the server and in-scope devices, as well as communication between the devices themselves.
Inbound Ports
Devices with an installed Tenable Patch Management client require the following inbound ports.
| Port | Protocol | Listening Process | Description |
|---|---|---|---|
| 34324 | UDP | AdaptivaClientService.exe | Replies from the server and clients. |
| 34325 | UDP | AdaptivaClientService.exe | Messages from server to client. |
| 34329 | UDP | AdaptivaClientService.exe | All broadcast messages from client to client. |
| 34546 | UDP | AdaptivaClientService.exe / and the system process | Transfer control port and IP2P control signals. |
| 34750 | UDP | AdaptivaClientService.exe and the system process | All WAN or Internet Peer to Peer content transfers. |
| 34760 | UDP | AdaptivaClientService.exe and the system process |
All LAN content transfers. |
| 34760 | TCP | N/A | The port used by TenablePatchP2PClientInstaller.msi. |
.
Outbound Ports
Devices with an installed Tenable Patch Management client require the following outbound ports when communicating over the Internet.
| Port | Protocol | Usage |
|---|---|---|
| 80 | HTTP |
Operations Manager and Cloud Relay Servers which relay client messages between Internet-based clients and the on-premises server. |
| 443 | HTTP | Operations Manager, Cloud Relay servers and patch content locations on a content delivery network (CDN). |
| 3478 | UDP | Cloud relay servers only. |