Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 5200 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

Web Control - Host Names in the Exceptions List

Monkster

Hi,

We run an internal website for employees which is normally accessed via the hostname rather than IP address. I would like to add the host name to the Allow list on the Web Control Exceptions list, but it doesn't allow this since there is no .com, etc in the address.

I assume there is no way around this. However would it be possible to have this added in future releases?

Thanks!

Stephen. 



This thread was automatically locked due to age.
Parents
  • 0

    Hello,

    What are you trying to guard against with this exclusion?

    If it's an internal IP, as far as I can gather, the only thing that will happen is content scanning.  SXL lookups to Sophos for an internal site will not happen as Sophos Labs wouldn't have any classification regarding a private site.

    To avoid content scanning, you can add a website authorization for the site by IP under the SAV policy.

    Hope it helps.

    Regards,

    Jak

  • 0 in reply to jak

    Hi,

    Thanks for the reply.

    It's an internal server, but some staff access are remote homeworkers who connect via VPN. I had wondered if there was a performance overhead/slow down on some already slow broadband connections for these remote workers who access the site. Putting an exclusion on it would just avoid those computers from trying to check if the site is okay, since we are happy that it is.

    I have already added the IP address anyway, but most users are accessing the site via hostname rather than IP.

    Thanks,

    Stephen.

Reply
  • 0 in reply to jak

    Hi,

    Thanks for the reply.

    It's an internal server, but some staff access are remote homeworkers who connect via VPN. I had wondered if there was a performance overhead/slow down on some already slow broadband connections for these remote workers who access the site. Putting an exclusion on it would just avoid those computers from trying to check if the site is okay, since we are happy that it is.

    I have already added the IP address anyway, but most users are accessing the site via hostname rather than IP.

    Thanks,

    Stephen.

Children
  • 0 in reply to Monkster

    Hi,

    If the IP is excluded that should work if they access it via the name also.

    As a test, you could host the test file eicar.com on the server and have users access it from the clients.  For example:

    Go to: http://www.eicar.org/86-0-Intended-use.html to get the Eicar string.  it starts X5O...

    Paste it into a new text document and save the file on the web server in question as "eicar.com".
    Note: If SAV is on the server you might have to exclude the location on disk you are saving it to so the on-access scanner on the server doesn't pick it up.

    Then, from the clients you can access it via, for example:

    http://ip/eicartest/eicar.com and http://fqdn/eicartest/eicar.com and http://hostname/eicartest/eicar.com.

    With the site authorised, the clients should be able to download the test file.  It will get detected by the on-access scanner as it's written to the "downloads" location on the clients but it will not be detected before it hits the browser by web protection if the exclusion is working.

    Hope it helps.

    Regards,

    Jak

Unfiltered HTML