Google QUIC traffic blocked?

[pmc]

We're getting a lot of blocked traffic on UDP port 80 and 443. From looking into it this is Google's new QUIC protocol over Chrome.

What is everyone else doing in this case? I'd prefer not to allow all UDP traffic over port 80 & 443. Any chance off an App-ID for this?

[dburns · Accepted solution]

There is already an application signature for QUIC in the current app database.

Dominic

[HITSSEC]

Hello we started seeing Google using the quic application to download Gmail attachments to the client's desktop. This application was not decrypted using a forward proxy and thus did not give us visibility for file attachments being downloaded within GMail.  Does create a blind spot and thus pose a risk.  Will try blocking it to see the impact is.

Phil

[pmc]

Can't believe I missed that! thanks

[Kerry_Knight]

So my next question would be,   when will URL filtering be applied to QUIC connections? It appears to currently be an all or nothing proposition. 

If you allow QUIC today for the performance benefits, if there are sites your company policy denies with URL Filtering, if they support QUIC, all users can get around your policy. Seems to be a loophole that should be addressed,  and not by the simple answer of Disable QUIC. QUIC is likely to become more popular, not less. 

[Raido_Rattameister]

Thing is that Palo does not support quic decryption. So all Palo can do to identify URL is to read what is on certificate (actual website request goes inside encrypted tunnel).