Q: What are the Firewall Rules for Silo Connections?
A: This document provides connection information, which might be needed to allow Silo to work properly from behind a firewall. If your network utilizes a firewall to limit outbound traffic, you may need to white list our IP ranges.
Domain names can be broadly white-listed using a wildcard entry as shown in the following examples:
Silo uses a TLS connection over port 443 (HTTPS). In rare instances, if you have existing network provisions for non-HTTPS traffic over port 443 (e.g. port redirect), you may not be able to connect to Silo without creating a Firewall exception for our service.
SSL Inspection Rules
If your firewall performs SSL inspection, you will need to disable this for Silo connections.
NOTE: This rule does not apply to Silo Windows Client version 2.9.13 and newer. Please see this article:
https://authentic8.freshdesk.com/a/solutions/articles/16000100713 for additional information.
Please note that in some cases, customers may need to whitelist our External API in order to use some Silo services. The domain to be whitelisted is: extapi.authentic8.com
Please make sure to allow access to TCP port 443 to the following list of IPs.
Web Client IP (a8silo.com):
Authentic8 registered IP space:
Third Party Provider IPs:
*If you are using the legacy load balancers, then you may need to white list the following IPs as well: