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

Sophos XG v17 does not block sophos test-sites

I tried to test our webfilter by browsing sophos' test sites (http://sophostest.com/). And it seems like the web filter does not block them.

Does Sophos' XG Product not work with those test sites any more? (i remember some early v16 firmwares to detect them)

 

Thanks for your Help :)

Lars Hartmann



This thread was automatically locked due to age.
Parents Reply
  • Mine is doing the same thing on certain test sites and it is once again poor categorization using the Sophos database vs McAfee like UTM. Mine is configured correctly. I cannot speak for the OP but you can see the screen shot show the category is wrong.  and  please have your web team check the categories of your test site. I do not see a reason we should have to submit those to you since it is your test site.

Children
  • I am also able to download the pdf test files which my kaspersky tries to block while sandstorm and sophos engines are asleep.

  • Turns out the Categorization is wrong - this is where i ask myself - why does sophos even offer these test-sites if their own products don't categorize them correctly?

    Example: http://sophostest.com/adult/index.html is categorized as "Information Technology":

  • Sophos has multiple products with different categorizations.  The sophostest.com uses different urls to test per product.  You must use the XG urls if you want to test XG.

     

    SWA:
    Endpoints controlled by SEC:
    http://www.sophostest.com/

     

    UTM:
    http://www.sophostest.com/utm/

     

    CWG:
    XG 17 and later:
    http://www.sophostest.com/cwg/

     

    Note: sophostest.com is only used for products that use SXL.  Therefore UTM prior to 9.1 or with local database does not have any.  And XG prior to v17 does not (it uses WINGc rather than SXL)

  • Hi Michael,

    What is WINGc and SXl?

    Regards, Ronak.

  • Cyberoam and XG prior to v17 connected to a cloud service that was originally built by Cyberoam.  The client is called WINGc and the server is WINGs.  This appliance sends the URL to the cloud, and the cloud responds with the categorization and application for that URL.  All answers it gives are from the native Cyberroam/Sophos data team.

    SXL is also a cloud categorization system, built by Sophos.  It is used by many different systems and does several different things, including URL category/application classification.  It can provide answers based on several different categorization databases depending on the product.

    SXL is superior.  It has better caching, better scaling, is faster, we have better monitoring, etc.

     

    However for admins and end users, they won't really see any difference at all except potentially better performance.

  • Thank you very much for your answer :-)

    It would be helpful to mention this on sophostest.com - as i for myself would have never found the /cwg/ site.

    Cheers

    Lars Hartmann

  • I agree with Lars. I use to sophostest.com and I did not know about different variants for different products.

    I think three links or buttons would solve the problem. 

    alda

  • While I don't mind using different sites for different products, its pure laziness on sophos' part not to categorize all those sites correctly on all their products. I can see if there are specific av tests for different products where it is actually not a virus and avira missing such test but on categorization there is no excuse. If there is a test site, all products should detect/categorize those urls correctly. Afterall they are hosted by sophos and are only relevant to sophos products.

    I generally like XG v17 and sxl categorization has improved my overall surfing experience but the backend data will need constant improvements to compete with other products on the market. When sophos misses their own website, it doesn't give me very much confidence in the quality and specially accuracy of the backend data.