Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 28 subscribers
  • Views 1876 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

sophostest.com - unable to test due to Sophos Scan exclusion recommendations

LHerzog

Hey, I cannot test our XG with the test site, you are providing: https://sophostest.com/

I've asked this once but forgot. Today I wanted to verify something but could'nt even find the request in the web filter log.

Of course, I could browse all the bad test sites.

This is because your test site is running on the same could servers, probably cloudfront.net, as you use for Sophos / Central services. And for those cloud servers (FQDN) there are http/https exceptions and the requests are not even scanned by webfilter.

Bad design for a (malware) test-site.

Can you please put the site on some stand-alone server so we can use it for testing the filters?

during my tests the site had the IP

13.225.87.17


This thread was automatically locked due to age.
  • 0 in reply to LuCar Toni

    that's a lot of work to get the xml version I see now, need all Objects and also NAT rule. will not get it done today.

    But why don#t you see the relation?

  • 0 in reply to LHerzog

    Yes. And what is the relationship to sophostest.com which is not related to *.sophos.com. There is a wildcard and a dot, separating everything infront of .sophos.com. sophostest.com is a own domain with other IP addresses. You showing a 13. IP, how does this IP correlate to those IPs related to sophostest.com? 

    __________________________________________________________________________________________________________________

Cookie Information Banner