Eventually, you might have set up content filtering but have encountered that when using Google Chrome Browsers, Google-related services such as YouTube are not efficiently blocked. Still, on other browsers, it works perfectly fine, blocking these services. How come, and what can you do to prevent this from happening?
Google Chrome uses the general transmission protocol called QUIC, whose primary goal is to improve the performance of applications, usually using HTTPS. Instead of using TCP port 443, QUIC uses UDP port 443 to initiate the handshake, making it way faster.
Google-related services support QUIC, and also other websites are getting into it nowadays, so the question remains: What can I do about it?
Google Chrome uses the general transmission protocol called QUIC, whose primary goal is to improve the performance of applications, usually using HTTPS. Instead of using TCP port 443, QUIC uses UDP port 443 to initiate the handshake, making it way faster.
Google-related services support QUIC, and also other websites are getting into it nowadays, so the question remains: What can I do about it?
The answer is simple: If the Content Filter cannot block YouTube or other Google-related pages, you can create a firewall rule to block UDP 443 to get it using TCP (as a fallback solution in case QUIC fails) to connect with the server. This will make the content filter get a grip on the traffic again, thus creating a block working efficiently.
Below is a screenshot of how this firewall rule could/should look like:
For more information, check this article: Firewall-Configuration on your Nebula Security Gateway (NSG)