Firewall Ports
You might need to open the following ports on your DMZ firewall, depending on your network configuration:
| Port | Protocol | Direction | Required for |
|---|---|---|---|
| 20 | TCP | Out | FTP over HTTP |
| 20 | FTP | In/Out | Backup & Restore and Transaction Log Export if you are using an FTP server located beyond the firewall. |
| 21 | SFTP | In/Out | Backup & Restore and Transaction Log Export if you are using an SFTP server located beyond the firewall. |
| 22 | TCP | In | SSH access to the |
| 22 | SFTP | Out | Backup & Restore, and, server containing lexical data for import |
| 25 | TCP | Out | Outbound SMTP. If your system uses an alternative port, open that instead. |
| 53 | UDP/TCP | Out | DNS requests, if using DNS servers beyond the firewall. Only allow outbound requests to the specified DNS servers, and responses from those servers. |
| 80 | TCP |
Out |
Access to Clearswift product and Operating System updates at repo.clearswift.net and rh.repo.clearswift.net |
| 80 |
TCP |
Out | HTTP access to the Sophos, Avira, or Kaspersky Update Servers for fetching anti-virus updates and software upgrades. Sophos update servers: Avira update servers: aav-update-1.clearswift.net, aav-update-2.clearswift.net, aav-update-3.clearswift.net, aav-update-4.clearswift.net, aav-update-5.clearswift.net, aav-update-6.clearswift.net, *.apc.avira.com Kaspersky update servers: |
| 80 | TCP | Out | HTTP access to the |
| 80 | TCP | Out | Access to the Service Availability List: services1.clearswift.net, services2.clearswift.net, services3.clearswift.net |
| 80 | TCP | Out | Access to the RSS Feed from www.clearswift.com |
| 80 | TCP | Out | Access to URL Database Updates: url1.clearswift.net, url2.clearswift.net, url3.clearswift.net, url4.clearswift.net |
| 88 | TCP/UDP | Out | User authentication using Kerberos |
| 123 | UDP | In/Out | Access to NTP services, if configured. The following servers are configured by default: 0.rhel.pool.ntp.org, 1.rhel.pool.ntp.org, 2.rhel.pool.ntp.org, 3.rhel.pool.ntp.org. |
| 135 | TCP | Out | User authentication using NTLM |
| 137 | UDP | Out | User authentication using NTLM |
| 139 | TCP | Out | User authentication using NTLM |
| 162 | UDP | Out | SNMP traps |
| 389 | TCP | In/Out | LDAP directory access (if you use LDAP servers beyond the firewall) |
| 443 |
TCP |
In/Out | HTTPS access to the |
| 443 | TCP | Out | HTTPS lexical data import |
| 443 | TCP | Out | Outbound HTTPS traffic |
| 443 | TCP | In/Out |
Kaspersky KSN lookup. (While this is using port 443, the traffic is not standard HTTP/S. Do not try to route through an SSL proxy.) The KSN lookup servers are: ksn1.kaspersky-labs.com, ksn2.kaspersky-labs.com, ksn3.kaspersky-labs.com, ksn4.kaspersky-labs.com |
| 443 | TCP | Out | HTTPS access to the |
| 443 | TCP | Out | HTTPS Lexical data import |
| 443 | TCP | Out | General HTTPS web access |
| 445 | TCP | Out | User authentication using NTLM |
| 514 | TCP | Out | Access to the central SYSLOG server (log export) |
| 636 | TCP | Out | LDAP and SSL connection to a non-global catalog port (if you are using LDAP servers beyond the firewall) |
| 636 | TCP | In | Secure LDAP directory access |
| 990 | FTPS | In/Out | Backup & Restore and Transaction Logging. Also used to connect the |
| 1270 | TCP | In/Out | SCOM server access: the port used by a SCOM server when monitoring the Gateway |
| 1344 | TCP | In | ICAP service |
| 3268 | TCP | Out | LDAP connection to an active directory global catalog port (if you are using LDAP servers beyond the firewall) |
| 3269 | TCP | Out | LDAP connection to an active directory global catalog port (if you are using LDAP servers beyond the firewall) |
| 3269 | TCP | In/Out | LDAP and SSL connection to an active directory global catalog port (if you are using LDAP servers beyond the firewall) |
| 8444 | TCP | In | Local HTTPS server |
| 9000 | UDP | In/Out | Distribution of time-based policy information to Peer |