We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X


This Product is Going End-of-Life and End-Of-Support

End-Of-Sales: As of December 1st, 2018, all new sales for Barracuda NextGen Firewall X Series products have ceased. Only renewals of software and hardware subscriptions for a maximum of one year are available for a limited time up to an expiration date of 30th November 2020.

End-Of-Life and End-Of-Support on December 1st 2020: All Barracuda Firewall X-Series sales will cease; neither new sales nor any renewals will be available. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support and services until your contract expires, or until Dec 1st, 2020, whichever occurs first. Please see the End-Of-Life definition as described in the End of Support and End of Life Information.

How to Configure Google Accounts Filtering in the Firewall

  • Last updated on

The X-Series Firewall can filter traffic to Google services based on the domain attached to the G Suite account. This allows you to block access to personal Google accounts and other non-whitelisted G Suite accounts, while still allowing your whitelisted G Suite domains. Google Accounts are enforced on a per-access-rule basis. Since Google requires HTTPS for almost all services, SSL Inspection is required. Google Chrome uses the QUIC protocol by default to communicate with Google servers. To force Chrome to use the HTTPS fallback, you must block QUIC traffic.

Before you begin

Step 1. Add your domains to the Google domain whitelist

Google accounts using the domains in the whitelist will be exempted from filtering when a Google account-enabled access rule matches.

  1. Go to FIREWALL > Settings.
  2. Make sure that Application Control is enabled.
  3. In the Google Accounts section, add domains to the Domain White List. Click + after each entry.
  4. Click Save.

Step 2. Create an access rule to block non-whitelisted Google accounts

You can block Google accounts not on the whitelist for all web traffic that matches an access rule by enabling Google Accounts in the advanced settings of the access rule.

  1. Go to FIREWALL > Firewall Rules.
  2. Create an access rule with the following settings:
    • Action – Select Allow.
    • Connection – Select Dynamic SNAT.
    • Source – Select the source addresses of the traffic.
    • Network Services – Select HTTP+S.
    • Destination – Select Internet.
  3. Enable Application Control and SSL Inspection.
  4. In the Add/Edit Access Rule window, click the Advanced tab.
  5. (optional) Set additional matching criteria:
  6. In the Other section, set Google Accounts to Yes.
  7. Click Save.
  8. Drag and drop the access rule in the ruleset, so that no access rule above it matches this traffic.

Step 3. Block QUIC for Google Chrome browsers

To force Google Chrome browsers to use HTTPS instead of QUIC on UDP port 443, you must create a BLOCK access rule.

  1. Go to FIREWALL > Firewall Rules.
  2. Create an access rule with the following settings:
    • Action – Select Block.
    • Connection – Select Dynamic SNAT.
    • Source – Add the source addresses of the traffic. Use the same source as the access rule in step 2.
    • Network ServicesCreate and select the service object for UDP 443. For more information, see Service Objects.
    • Destination – Select Internet.
  3. (optional) Set additional matching criteria:
    • Valid for UsersUse the same user object as in step 2.
    • Apply only during this timeUse the same schedule object as in step 2.
  4. Click Save.
  5. Drag and drop the access rule above the rule created in step 2.

Web traffic matching this rule can now only access Google accounts for domains that are included in the whitelist. When users access a non-whitelisted domain, they are automatically redirected to a Google block page.


Last updated on