Yeah but > Palo Alto Networks recommends creating a security policy in the firewall to block the QUIC application. With the QUIC traffic getting blocked by the

Yeah but > Palo Alto Networks recommends creating a security policy in the firewall to block the QUIC application. With the QUIC traffic getting blocked by the Firewall, the Chrome browser will fall back to using traditional TLS/SSL. Note that this will not cause the user to lose any functionality on their browser. Firewall gains better visibility and control of Google applications with or without the SSL decryption enabled. https://docs.paloaltonetworks.com/best-practices/10-2/decryption-best-practices/decryption-best-practices/deploy-ssl-decryption-using-best-practices https://docs.paloaltonetworks.com/best-practices/10-2/decryp... https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClarCAC https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?... Fortinet also recommends blocking it. > However, due to the protocol is still in an experimental stage, it is not supported by Fortinet and causes some issues when SSL inspection profiles are needed to block specific websites or applications provided by Google itself. https://community.fortinet.com/t5/FortiGate/Technical-Note-Disabling-Blocking-QUIC-Protocol-to-force-Google/ta-p/191657?externalId=FD36529 https://community.fortinet.com/t5/FortiGate/Technical-Note-D... And given how trivial and likely udp/443 is already blocked because the only reason prior to QUIC you would be hitting udp/443 is some malware trying to get past the firewall and hoping it's open without inspection turned on you're fighting an uphill battle.