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 on this page. For details, see Proxy settings.

In addition to the ports on this page, Deep Security uses ephemeral ports when opening a socket (source port). Under rare circumstances these may be blocked, causing connectivity issues. For details, see Activation Failed - Blocked port.

Deep Security port numbers

The following diagram shows the default ports in a Deep Security system. For details, see the table below the diagram.

Port type Default port number
Deep Security as a Service listen ports
  • 443/HTTPS (Deep Security as a Service heartbeat listen port)
Deep Security as a Service destination ports
  • 80/HTTP, 443/HTTPS (these ports are used by various Deep Security cloud services, Smart Protection Network services, AWS API, and Azure API)
  • 514/Syslog* (SIEM or syslog server port)
  • 4118/HTTPS* (Deep Security Agent port)
  • 4122/HTTPS* (Deep Security Relay port)

* Notes:

Deep Security Agent listen port
  • 4118/HTTPS (Agent listen port for heartbeats)

4118 can be closed if you are using agent-initiated communication. By default, agent-initiated communication is used, so 4118 can be closed. See Agent-manager communication for details.

Deep Security Agent destination ports
  • 53/DNS (DNS server port)
  • 80/HTTP, 443/HTTPS (Smart Protection Network port, Deep Security as a Service port )
  • 123/NTP* (NTP server port)
  • 514/syslog* (SIEM or syslog server port)
  • 4122/HTTPS* (Deep Security Relay port)
  • 5274/HTTP, 5275/HTTPS* (Smart Protection Server ports)

* Notes:

Deep Security Relay listen ports

Relays are not required because Deep Security as a Service provides hosted ones. If you do decide to host relays in your local environment, then make sure the following relay listen ports are open. For details on why you might choose to use local relays, click here.

  • Open all the agent listen ports, since they apply to the relay as well
  • 4122/HTTPS (relay port)
  • 4123 (port for communication between the agent and its own internal relay)

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

Relays are not required because Deep Security as a Service provides hosted ones. If you do decide to host relays in your local environment, then make sure the following relay destination ports are open. For details, see Define relays to distribute updates.

  • 80/HTTP, 443/HTTPS (Trend Micro Update Server/Active Update and Download Center ports)
  • 4122 (port of other relays)

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
Deep Security as a Service, agents, relays Deep Security as a Service
  • app.deepsecurity.trendmicro.com
  • agents.deepsecurity.trendmicro.com
  • dsmim.deepsecurity.trendmicro.com
  • relay.deepsecurity.trendmicro.com

In the list above, app.deepsecurity[...] is the Deep Security as a Service URL, agents.deepsecurity[...] and dsmim.deepsecurity[...] are the Deep Security as a Service heartbeat server URLs, and relay.deepsecurity[...] is the URL of the relays hosted by Deep Security as a Service.

API clients Deep Security APIs
  • app.deepsecurity.trendmicro.com/webservice/Manager?WSDL
  • app.deepsecurity.trendmicro.com/api
  • app.deepsecurity.trendmicro.com/rest
Deep Security as a Service, agent, and relay

Download Center or web server

Hosts software.

  • files.trendmicro.com
Deep Security as a Service

Smart Protection Network -
Certified Safe Software Service (CSSS)

Used for event tagging with Integrity Monitoring.

  • gacl.trendmicro.com
  • grid-global.trendmicro.com
  • grid.trendmicro.com
The agent

Smart Protection Network -
Global Census Service

Used for behavior monitoring, and predictive machine learning.

  • dsaas1100-en-census.trendmicro.com
The agent

Smart Protection Network -
Good File Reputation Service

Used for behavior monitoring, predictive machine learning, and process memory scans.

  • deepsecaas11-en.gfrbridge.trendmicro.com
Deep Security as a Service Smart Protection Network -
Smart Feedback

12.0 and higher

  • ds120-en.fbs25.trendmicro.com
  • ds120-jp.fbs25.trendmicro.com

11.0 and higher

  • deepsecurity1100-en.fbs25.trendmicro.com
  • deepsecurity1100-jp.fbs25.trendmicro.com

10.0

  • deepsecurity1000-en.fbs20.trendmicro.com 
  • deepsecurity1000-jp.fbs20.trendmicro.com
  • deepsecurity1000-sc.fbs20.trendmicro.com
The agent Smart Protection Network -
Smart Scan Service
  • dsaas.icrc.trendmicro.com
The agent

Smart Protection Network -
predictive machine learning

  • dsaas-en-f.trx.trendmicro.com
  • dsaas-en-b.trx.trendmicro.com
The agent Smart Protection Network -
Web Reputation Service
  • dsaas.url.trendmicro.com
Deep Security as a Service Help and support
  • help.deepsecurity.trendmicro.com
  • success.trendmicro.com/product-support/deep-security
Deep Security as a Service Licensing and registration servers
  • licenseupdate.trendmicro.com
  • clp.trendmicro.com
  • olr.trendmicro.com
Deep Security as a Service News feed
  • news.deepsecurity.trendmicro.com
  • news.deepsecurity.trendmicro.com/news.atom
  • news.deepsecurity.trendmicro.com/news_ja.atom
Browser on agent computers and the computer used to log in to Deep Security as a Service Site Safety

Optional. There are links to the URLs below within Deep Security as a Service UI and on the agent's 'Your administrator has blocked access to this page for your safety' page.

  • sitesafety.trendmicro.com
  • jp.sitesafety.trendmicro.com
Deep Security as a Service, agent, and relay

Update Server (also called Active Update)

Hosts security updates.

  • iaus.activeupdate.trendmicro.com
  • iaus.trendmicro.com
  • ipv6-iaus.trendmicro.com
  • ipv6-iaus.activeupdate.trendmicro.com
Deep Security as a Service

AWS and Azure URLs

Used for
adding AWS accounts, Azure accounts and to Deep Security as a Service.

 

AWS URLs

  • URLs of AWS endpoints listed on this AWS page, under these headings:
    • Amazon Elastic Compute Cloud (Amazon EC2)
    • AWS Security Token Service (AWS STS)
    • AWS Identity and Access Management (IAM)
    • Amazon WorkSpaces

Azure URLs

  • login.windows.net (authentication)
  • management.azure.com (Azure API)
  • management.core.windows.net (Azure API)

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.

Deep Security as a Service

Telemetry service

  • telemetry.deepsecurity.trendmicro.com

Deep Security as a Service IP addresses

If you need to restrict the IP addresses that are allowed in your environment, read this section.

If a firewall or AWS security group restricts outbound traffic from your network, you must configure the firewall to allow traffic outbound on port 443 to these Deep Security as a Service IPv4 addresses.

Deep Security as a Service sends data from its job nodes on subnet 34.205.5.0/27. If you configured a SIEM or syslog server, make sure it is able to receive inbound traffic from that subnet on your syslog port (by default, 514). Also, if you configured your agents to use bidirectional or manager-initiated communication, then make sure your agents are also able to receive traffic from 34.205.5.0/27 on the agent listen port (by default, 4118). (By default, agents use agent-initiated communication.)

By default, Deep Security as a Service uses Trend Micro's cloud-based Smart Protection Network which does not have static IP addresses. If you want to use the Smart Protection Network but need to restrict your outbound communication, we suggest you deploy a Smart Protection Server in your environment. For information on how to do this, see Deploy a Smart Protection Server in AWS.

Source Purpose Destination IP addresses
Administrator's computer and agents GUI for Deep Security as a Service

34.198.27.224

34.205.210.199

34.205.239.162

50.17.162.194

52.0.124.201

52.0.33.128

52.72.111.249

52.72.211.36

52.87.46.150

52.207.138.122

54.80.120.113

54.175.211.84

Agents and relays Security package updates

34.194.74.60

34.196.197.189

34.204.219.38

34.205.83.195

52.2.63.133

52.21.149.243

52.44.144.238

52.55.188.35

52.201.199.128

52.206.54.30

54.86.152.157

54.87.173.241

Agents Heartbeat

34.192.67.219

34.196.25.105

34.199.44.254

34.204.244.61

34.206.23.113

34.206.95.140

34.206.146.6

34.206.215.233

52.23.102.52

52.54.141.100

52.54.240.176

54.86.2.200

Agents Fast heartbeat

34.192.145.157

34.199.111.255

34.204.221.63

34.206.179.241

52.44.129.132

52.45.95.227

52.55.183.116

52.73.88.81

52.202.143.169

52.206.208.21

54.208.106.230

54.152.108.196