Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 40 subscribers
  • Views 3129 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

Allow block site for user

Munish thakur

A user is trying to connect to  https://help.virginatlantic.com/gb/en.html  which is in travel category and allowed in rule 

But on browser user get message that site is blocked by sophos .

By Checking the log i Find one of my rule that is  for to  drop window update , in which i m using FQDN host method to drop traffic by entering different URL 

is also dropping   https://help.virginatlantic.com/gb/en.html .

And when i turn off my rule    site   https://help.virginatlantic.com/gb/en.html working fine .

My question is that how can i give access to https://help.virginatlantic.com/gb/en.html    without turn off my window update rule and i cant shift its position to down 

for all user    

 ....



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

    Using FQDN to block/allow traffic has such side effects. Let's assume you have blocked windows update by a block rule with *.microsoft.com as destination. This will block all sub domains of microsoft.com and it is possible one of subdomains are hosted on same public host as help.virginatlantic.com. This way help.virginatlantic.com will be blocked too. Nowadays most websites are hosted on shared public cloud  servers and with that, this issue is a common problem. You have to options here:

    1- Place allow rule in top of block rule as drikkotte suggested but this may cause windows update block rule useless.

    2- Block windows update using webfilter policy instead of FQDN. This way you could only block URLs with specific domain name instead of FQDN destination.

    Regards

    Farshid

Reply
  • 0

    Using FQDN to block/allow traffic has such side effects. Let's assume you have blocked windows update by a block rule with *.microsoft.com as destination. This will block all sub domains of microsoft.com and it is possible one of subdomains are hosted on same public host as help.virginatlantic.com. This way help.virginatlantic.com will be blocked too. Nowadays most websites are hosted on shared public cloud  servers and with that, this issue is a common problem. You have to options here:

    1- Place allow rule in top of block rule as drikkotte suggested but this may cause windows update block rule useless.

    2- Block windows update using webfilter policy instead of FQDN. This way you could only block URLs with specific domain name instead of FQDN destination.

    Regards

    Farshid

Children
No Data
Unfiltered HTML