QUIC is a new protocol designed by Google to make the web faster and more efficient. It's on by default in Google Chrome and used by a growing list of websites. Unfortunately, most, if not all, firewalls do not currently recognize QUIC traffic as 'web' traffic, therefore it is not inspected, logged or reported on, leaving a gaping hole in your network's security.
This article describes how QUIC works, its current consequences on network security and reporting, and how you can resolve the issues associated with QUIC.
Google has always been obsessed with speed and over the years they have made numerous efforts to make the web more efficient and more performant. The new kid on the block for performance improvement is a protocol named QUIC. Where SPDY and HTTP/2 were iterative improvements on HTTP over TCP, QUIC is a different approach using UDP as the transport protocol.
QUIC is essentially HTTP/2 over UDP which is a new layer4 protocol.
At the time of writing this article, QUIC is still 'experimental', but is enabled by default in Google Chrome, and can be enabled in Opera 16. Other browsers will surely follow once the protocol is finalized. It is implemented on all Google web properties such as Google Search, YouTube, Gmail, Drive etc, and is being adopted by a growing list of other websites.
The issue is not with the protocol or the technology itself. The supposed upside of QUIC is that it makes web communications more efficient and faster. The problem is that it is not supported by security appliances such as firewalls yet, and has therefore inadvertently created a security hole for many organizations.
Most firewalls have extensive functionality when dealing with HTTP and HTTPS traffic. In most architectures, when HTTP traffic is detected, it is passed on to a web protection module that performs web filtering, deep packet inspection etc. HTTP traffic gets special treatment because the firewalls can interpret the traffic from Layer4 up to layer 7. This special treatment includes malware scanning and in most cases, enhanced reporting.
QUIC uses the traditional HTTP ports of 80 and 443 but that is where the similarities end. The supporting browsers and servers support this new protocol and are able to process it as web traffic, but the network device in between cannot determine the application protocol and switches to treating it like any generic layer 4 UDP traffic.
QUIC traffic is therefore not scrutinized as it should be and it is not forwarded to the firewall's web protection features.
The images below compare the Wireshark capture of traditional HTTPS TLS traffic with QUIC.
The real world implications of QUIC traffic range from not being able to restrict access to YouTube or enforce Google Safe Search, through to malware or ransomware being downloaded through Gmail or any other QUIC enabled website.
To compound the issue, you will most likely not be aware of any problems since the logging and reporting engines tied to the web protection features are also affected.
To further complicate things, the standards have not been locked down yet and the protocol is frequently revised, which is a reason why firewalls have not yet caught up.
From a reporting perspective, this means you cannot log and report on the full URLs of QUIC traffic, such as Google Search or YouTube, meaning search term alerts, or viewing a list of YouTube videos watched is not possible when QUIC is enabled.
Since the different firewalls do not recognize QUIC traffic as web traffic, they typically only log the traffic in their firewall log as generic UDP traffic. This means that the rich logging data we expect from HTTP traffic is not generated, logged or sent out via syslog.
Here is an example of normal TCP web traffic being detected by the Sophos XG firewall module and being passed onto the web protection module. Note how the firewall log contains relatively little data compared to the Webfilter log that records details such as URL, site cetegory etc.
Here is an example of the same site being accessed using QUIC. The firewall logging is still there but the web logging is not. All of the rich logging information is gone.
Products such as Fastvue Reporter rely on the ability of the firewall to correctly identify and log the web traffic. If you have seen a recent decline in traffic to and from Google sites (including YouTube, Gmail, Drive etc) there is a high probability that your firewall is allowing QUIC.
Did you know: Fastvue Reporter produces clean, simple, web usage reports using log data from your UTM or firewall that you can confidently send to department managers and HR team. It also helps to to support IT and network security teams with managing bandwith, reducing IT workload and troubleshooting with ease thanks to live alerts, dashboards and scheduled reports.
The good news is that if QUIC communication does not work between a client and a server, the traffic will fall back to traditional HTTP/HTTPS over TCP, where it can be inspected, controlled, logged and reported on as usual.
At the time of writing, the advice from most firewall vendors is to block QUIC until support is officially added to their products. This recommended method will vary from firewall to firewall. Some firewalls allow QUIC by default while others block it by default, but all firewalls are able to allow or block it.
Common methods are to block either a defined QUIC protocol, QUIC application type, or create a firewall rule to block UDP on port 80 and 443. We suggest you seek guidance from your firewall manufacturer for recommended actions.
Here are some guides on blocking QUIC with some popular firewalls:
Before you block UDP on port 443 consider the following. Using HTTP packets over UDP is not new or even unique to QUIC. OpenVPN which provides SSL VPN is capable of using either TCP or UDP as the transport. Have a look at the UDP users on the network and determine if it is safe to block all UDP traffic on port 443.
At the time of writing this article, QUIC is enabled by default when you use the Google Chrome browser, and you can enable QUIC in Opera 16. All the other major browsers do not yet support QUIC. But as Chrome currently claims 60% of the web browser market, this is not a point to ignore.
There was a time when only Google properties were implementing QUIC, such as Google Search, YouTube, Gmail and so on. However as it is an open protocol, it is now in use by a growing list of popular websites (such as meetup.com), as well a growing list of bad actors as they catch on to the fact that QUIC is a great way to effectively bypass malware scanners and content filters. So this point especially cannot be ignored!
Depending on the configuration of your browser and firewall, you may be using QUIC without even knowing it. The simplest test to see if you QUIC is enabled in your environment is to use the Developer Tools native in the Chrome browser. Go to the Network tab, ensure you include the Protocol column, and then browse to any of the Google sites such as https://www.google.com
If you see items with the Protocol http/2+quic/39 then you are using QUIC.
You can also view active QUIC sessions by entering chrome://net-internals/#quic in your address bar. Alternatively, you can add a Chrome browser extension to indicate which pages are served by QUIC.
You can also disable QUIC in your browser, by going to entering chrome://flags in your address bar, and setting the Experimental QUIC protocol option to Disabled.
Despite everything above, QUIC is generally a good thing for the world as it makes web communications more efficient and faster between a browser and the server, and who doesn't want their web pages to load faster, and to have less buffering when watching adorable puppy videos on YouTube?
However, the general consensus (at least for now) is that there is no noticeable difference for the average user when QUIC is enabled.
The websites will still work, so you might as well choose security over a tiny increase in performance.
To summarize, QUIC is a new protocol designed by Google to make the web faster and more efficient. It's on by default in Google Chrome and used by a growing list of websites. Unfortunately, most, if not all, firewalls do not currently recognize QUIC traffic as 'web' traffic, therefore it is not inspected, logged or reported on, leaving a gaping hole in your network's security.
Blocking QUIC at the firewall will force the browser and server to fall back to standard HTTP/HTTPS, allowing the traffic to be inspected, protected and reported on as usual.
Now that you're clued in on QUIC, why not make your life easier and setup Fastvue Reporter? Fastvue Reporter consumes syslog data from UTMs and Firewalls and produces clean, simple, web usage reports that you can confidently send to department managers and HR team. Automate reports and get the job of reporting on web usage off your desk and into the hands of people that need it. Take a look at the benefits and features available to IT and network security teams to fully understand the capabilities of Fastvue Reporter and how it can assist your business.
Download the free 30 day trial, or schedule a demo and we'll show you how it works!
The Best SonicWall Configuration for Detailed Logging and Reporting
How to Enable Dark Mode in Fortinet FortiGate (FortiOS 7.0)