Deep Security 11 has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.
Port numbers, URLs, and IP addresses
Deep Security default port numbers, URLs, IP addresses, and protocols are listed in the sections below. If a port, URL or IP address is configurable, a link is provided to the relevant configuration page.
If your network uses a proxy or load balancer, you can configure Deep Security to use it instead of the default ports and URLs listed in sections below. For details, see Proxy settings
Deep Security port numbers
| Port type | Default port number |
|---|---|
|
|
|
|
|
* Notes:
|
| Deep Security Agent listen port |
4118 can be closed if you are using agent-initiated communication. By default, |
| Deep Security Agent destination ports |
When using the AWS AMI and Azure VM versions of the manager, open port 443 instead of port 4119. * Notes:
|
| Deep Security Relay listen ports |
Port 4123 should not be listening to connections from other computers, and you don't need to configure it in network firewall policies. But if you have firewall software (such as Windows Firewall or iptables) on the manager's server itself, verify that it does not block this connection to itself. Also verify that other applications do not use the same port (a port conflict). |
| Deep Security Relay destination ports |
When using the AWS AMI and Azure VM versions of the manager, open port 443 instead of port 4119. |
Deep Security URLs
If you need to restrict the URLs that are allowed in your environment, read this section.
You'll need to make sure your firewall allows traffic to the following: Trend Micro, Deep Security, AWS, and Azure server URLs on port 443 (HTTPS) and port 80 (HTTP).
| Source | Destination server or service name | Destination URL |
|---|---|---|
| SOAP and REST API clients | Deep Security SOAP and REST APIs |
|
| REST API clients | Deep Security Status Monitoring API |
|
|
|
Download Center or web server Hosts software. |
|
|
|
Smart Protection Network - Used for event tagging with Integrity Monitoring. |
|
| The agent |
Smart Protection Network - Used for behavior monitoring, and predictive machine learning. |
11.0 agents connect to:
10.2 and 10.3 agents connect to:
10.1 and 10.0 agents connect to:
|
| The agent |
Smart Protection Network - Used for behavior monitoring, predictive machine learning, and process memory scans. |
11.0 agents connect to:
10.2 and 10.3 agents connect to:
10.1 and 10.0 agents connect to:
|
| The agent | Smart Protection Network - Smart Feedback |
11.0 agents connect to:
10.0 agents connect to:
|
| The agent | Smart Protection Network - Smart Scan Service |
11.0 agents connect to:
10.2 and 10.3 agents connect to:
10.1 and 10.0 agents connect to:
9.6 and 9.5 agents connect to:
|
| The agent |
Smart Protection Network - Used for predictive machine learning. |
11.0 agents connect to:
10.2 and 10.3 agents connect to:
|
| The agent | Smart Protection Network - Web Reputation Service |
11.0 agents connect to:
10.2 and 10.3 agents connect to:
10.1 and 10.0 agents connect to:
9.6 and 9.5 agents connect to:
|
|
|
Help and support |
|
|
|
Licensing and registration servers |
|
|
|
News feed |
|
| Browser on agent computers and the computer used to log in to |
Site Safety |
Optional. There are links to the URLs below within
|
| The relay, |
Update Server (also called Active Update) Hosts security updates. |
|
|
|
AWS and Azure URLs Used for
|
AWS URLs
Azure URLs
The management.core.windows.net URL is only required if you used the v1 Azure connector available in Deep Security Manager 9.6 to add an Azure account to the manager. With Deep Security Manager 10.0 and later, a v2 connector is used, and does not require access to this URL. |
