This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
For fun, I asked AI Copilot this question. As Chris stated earlier, it is planned for R82.
HTTPS Inspection of QUIC (UDP/443) is not supported in R81.20. QUIC is a protocol that runs over UDP and is used by Google Chrome and other applications to improve performance. Since QUIC traffic is not treated as HTTPS, it bypasses HTTPS Inspection rules.
To handle QUIC traffic, you can take the following steps:
Disable QUIC in Google Chrome:
Open Chrome and typechrome://flagsin the address bar.
Search for "Experimental QUIC protocol".
Set it to "Disabled".
Click "Relaunch Now" to restart Chrome.
Block QUIC on the Firewall or Application Control Policy:
Firewall Policy:
Create a new UDP service on port 443.
Set a firewall rule to block this traffic.
Note: This will block all UDP traffic on port 443, not just QUIC.
Application Control Policy:
Set a rule to block the "QUIC Protocol".
For more detailed information, you can refer to the following SecureKnowledge articles:
sk111754: HTTPS traffic to Google services (over QUIC) from Chrome cannot be inspected by HTTPS inspection rules