Solved

Recommended Firewall URL/IP's for correct admin console reporting from installed base

  • 8 November 2017
  • 1 reply
  • 29 views

We are in the process of installing Webroot on our network. We have some shop PC's that I have it installed on but they are not reporting to the admin console that it is installed.
They are not reporting becasue they don't have internet access. What they do have is access to our company exchange servver to have email. So accessing that email server on our local network then opens up the possiblility of them getting something dangerous in an email.
What hole do I need to open in my firewall policy so those PC's can report to Webroot's admin console and get policy settings pushed to them?
icon

Best answer by WaymonB 10 November 2017, 00:54

View original

1 reply

Hi there, 
 
For firewalls all our traffic goes over port 80, 443, and SSH 22. We do not have any direct IP's for you to enter in as use AWS for our backend. We have a range of over 10 thousand IP's that can be pulled from  literally anywhere in the world (just wanted to note this incase your firewall is region locked). With that said, below are the wildcarded URL's that have to be allowed through for WSA to communicate properly.
 
*.webrootcloudav.com
(Please note: Some firewalls do not support double dotted subdomain names with a single wildcard mask (i.e. g1.p4.webrootcloudav.com being represented by *.webrootcloudav.com) so some environments might require either *.p4.webrootcloudav.com or *.*.webrootcloudav.com)
 
*.webroot.com
 
*.s3.amazonaws.com
 
WSAWebFilteringPortal.elasticbeanstalk.com
 
*.webrootanywhere.com
 
Hope this helps,
Waymon B.
Webroot Business Support.

Reply