By default, agent-initiated communication is used with Deep Security as a Service, so 4118 can be closed.

Open 4118 if you are using bidirectional or manager-initiated communication.

514 is configurable in the manager or Deep Security as a Service.

Open 514 if you want to forward Deep Security events to an external SIEM or syslog server.

389 and 636 are configurable in the manager if your Active Directory server uses a different port.

Open 389 and 636 if you want to add computers from Active Directory to the manager.

Open 123 if you want to synchronize the manager with an NTP server.

Note: Control Manager, Deep Discovery Analyzer, and VMware are only supported with Deep Security on-premise, and a Whois server is not necessary if you're using Deep Security as a Service. For the NSX and vCenter ports, click here. To configure the Control Manager and Deep Discovery Analyzer ports, click here. 80 and 443 are configurable depending on the service being accessed.

80 and 443 are used by various Deep Security cloud services, Smart Protection Network services, AWS API, Azure API, Control Manager, Deep Discovery Analyzer, VMware components (vCenter, ESXi, NSX), and Whois servers.

25 is configurable in the manager or Deep Security as a Service.

Open 25 if you want email notifications.

1521/SQL (Oracle database port click here or here for details).

1433/SQL (Microsoft SQL database port click here or here for details).

389/LDAP, 636/LDAPS* (Active Directory).123/NTP* (NTP server port the NTP server can be Trend Micro Control Manager).514/Syslog* (SIEM or syslog server port)ĭeep Security Manager (on-premise), Deep Security AMI for AWS Marketplace, and Deep Security VM for Azure Marketplace destination ports:.

4120/HTTPS (Deep Security Manager heartbeat and activation port)ĭeep Security AMI for AWS Marketplace ports:ĭeep Security VM for Azure Marketplace listen ports:ĭeep Security as a Service and Deep Security Manager destination portsĭeep Security as a Service destination ports:.

Also used for shared and global Application Control rulesets, unless your rulesets are downloaded from a relay.)

4119/HTTPS (Deep Security Manager GUI and API listen port.

Deep Security port numbers Port typeĭeep Security as a Service and Deep Security Manager listen portsĭeep Security as a Service listen ports):ĭeep Security Manager (on-premise) listen ports: For details, see Proxy settings and Load Balancers. 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.

If a port, URL or IP address is configurable, a link is provided to the relevant configuration page. Deep Security default port numbers, URLs, IP addresses, and protocols are listed in the sections below.

Pulse secure client which ports to open