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

Chrome allowing some users to bypass web filter

Hello!

We recently installed a XG210 onsite and have been learning on the fly, so forgive me if this is something obvious. 

In our Web Filter policy we have it set to block Video Hosting and Video Streaming sites. This filter is used in multiple firewall policies. It appears though that some users (myself included) are able to still visit www.youtube.com and view the site/videos as if the filter wasn't in place, but only in Chrome. In IE, Firefox and even a Chrome Incognito window the site is blocked. I've look at the live connections and I can see the connections to youtube.com but the Log Viewer does not show any Web Filter logs for youtube.com for users that are able to view it still. 

I've tried a lot of things but I can't figure it out. Does anyone have any good next steps I can try?

Thanks!

Devon

EDIT1: Version 15.01.0 MR3



This thread was automatically locked due to age.
Parents
  • Hi Devon,

    Thanks for choosing Sophos.

    Check #1.2 and verify which FW rule ID forwards the packet for the source. Post a screenshot of the FW rule ID and the policies defined inside it. Make sure that the FW rule has HTTPS and HTTP scan enabled. 

    Thanks

  • Hi Sachin,

    I've attached the screen shots below and I've also included two rows from the packet capture, one which has rule 26 applied and the other which does not have a rule applied right below it (though that may just be me not knowing how to read it).

    I've also noticed, that despite https decrypt and scan being enabled that the certificate from youtube in my chrome browser is direct from google and not a sophos mitm one.

    Cheers,

    Devon

    Time
    In Interface
    Out Interface
    Ethernet Type
    Source IP
    Destination IP
    Packet Type
    Ports[src,dst]
    Rule ID
    Status
    Reason
    Username
    Web Filter ID
    Application Filter ID
    IPS Policy ID
    User Group
    Bandwidth Policy ID
    Remote Access Policy ID
    Gateway ID
    Connection ID
    Master Connection ID
    Connection Status
    Served By
    Web Category ID
    Connection Flags
    Application ID
    Application Category ID
    2016-09-30 08:31:06
    Port1
    IPv4
    172.217.1.110
    172.16.50.161
    TCP
    443,62559
    26
    Generated
    devonn@.local
    12
    1
    5
    OU=Office,OU=,DC=,DC=local
    No Policy
    No Policy
    No Gateway
    1629948768
    0
    ASSURED
    CLOSE_WAIT
    61
    61
    100
    5
    2016-09-30 08:31:06
    Port1
    IPv4
    172.16.50.161
    172.217.1.110
    TCP
    62559,443
    26
    Consumed
    devonn@.local
    12
    1
    5
    OU=Office,OU=,DC=,DC=local
    No Policy
    No Policy
    1
    1629948768
    0
    ASSURED
    FIN_WAIT
    61
    1
    100
    5
    2016-09-30 08:31:06
    Port1
    IPv4
    172.16.50.161
    172.217.1.110
    TCP
    62559,443
    0
    Incoming
    -
    No Policy
    No Policy
    No Policy
    -
    No Policy
    No Policy
    No Gateway
    0
    0
    UNREPLIED
    NONE
    No Category
    0
    No Application
    No Category

       

  • sHI DevonNoonan , 

    I have my doubts on the history existed and the connection was no deleted from XG appliance 

    To check the connections in your network  console > system diagnostics utilities connections v4 show src_ip <ipaddress of Host machine>

    Note : The firewall rule would block new connections and would not interfere with existing connections . So even with HTTP Decrytion enabled , it would resume its connection with an existing connection .

    As per the policy configuration, you have added a Schedule on the Video Hosting sites and So that system might have resumed an existing connection with the same session ID.

    Could you test by deleting the connection during the Scheduled time by using the command  Console>system diagnostics utilities connections v4 delete src_ip <ipaddress of host machine>

    I would like to add an information , Youtube/ Google/apps related to google uses QUIC protocol that would operate on UDP : 443 and is applicable to Google Chrome. If you use any other browser then the connection would work on  TCP : 443. I would suggest you to create a Rule to Drop UDP: 443 . So the sessions  would be diverted to TCP 443 . 

    Thanks and Regards 

    Aditya Patel | Network and Security Engineer.

  • Hi Aditya,

    Dropping UDP:443 traffic did the trick, regardless of any already open connections! Now I just have to figure out if there is a way to filter out certain types of videos instead of all of youtube.

    Thanks for the help!

  • Hi Devon,

    I am having the same problem. How did you manage to setup the firewall rule to drop UDP port 443 traffic?

    Thank You!

  • You can create a UDP HTTPs definition and then create a policy to drop udp 443 traffic. Make sure that the blocking policy is applied BEFORE the allowed policy. I am using v16 so my screen may look different.

    On a side note, its generally considered good practice to ONLY ALLOW PROTOCOLS that you need and not use ANY ANY firewall policies.

Reply
  • You can create a UDP HTTPs definition and then create a policy to drop udp 443 traffic. Make sure that the blocking policy is applied BEFORE the allowed policy. I am using v16 so my screen may look different.

    On a side note, its generally considered good practice to ONLY ALLOW PROTOCOLS that you need and not use ANY ANY firewall policies.

Children
  • You can create a UDP HTTPs definition and then create a policy to drop udp 443 traffic. Make sure that the blocking policy is applied BEFORE the allowed policy. I am using v16 so my screen may look different.

    On a side note, its generally considered good practice to ONLY ALLOW PROTOCOLS that you need and not use ANY ANY firewall policies.

     

     

    Thank you, Billybob! The firewall is now working perfectly.

  • Encrypted UDP 443 traffic to Google is now recognized as QUIC and can be block with a check box in each individual Sophos XG firewall rule.

    Before this option in v.17 I used to create a "Block Google QUIC" rule at the top of my firewall rules to drop all UDP 443 traffic.