Hey @

 

You'll need to setup rules on the Sonicwall to allow communication to the following Domains to allow Webroot to communicate with it's services. 

 

webroot.com

webrootcloudav.com

webrootanywhere.com

prevx.com

amazonaws.com

cloudfront.net

webrootdns.net

wsawebfilteringportal.elasticbeanstalk.com

 

Cheers



John 

---

Thats fine I can just place those in the allowed domains...Thank you

---

@  If you've got any sway with Webroot, could you communicate this to their documentation and support teams?  Sonicwall Gateway AV's been blocking installer downloads from IP's that reverse-resolve to cloudfront.net addresses, but support swears up-and-down that these are the only 5 FQDN's that need to be allowed through firewall:



    *.webrootcloudav.com

    Agent communication and updates

    (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

    Agent messaging



    *.s3.amazonaws.com

    Agent file downloading and uploading



    WSAWebFilteringPortal.elasticbeanstalk.com

    Required for agent Web Filtering, elasticbeanstalk is an amazon AWS domain



    *.webrootanywhere.com

    Management portal and support ticket logs upload

---