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 CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

How to Configure Google Accounts Filtering in the Firewall

  • Last updated on

The F-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 Interception 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.

In this article:

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 CONFIGURATION > Configuration Tree > Box > Virtual Servers > Assigned Services > Firewall > Security Policy.
  2. Click Lock.
  3. In the Google Personal Accounts section, click + to add domains to the Domain White List.
    Google_accounts_01.png
  4. Click Send Changes and Activate.

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 Application Control settings of the access rule.

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > Firewall > Forwarding Rules.
  2. Click Lock.
  3. Either click the plus icon (+) at the top right of the ruleset, or right-click the ruleset and select New > Rule.
    FW_Rule_Add01.png
  4. Select Pass as the action.
  5. Enter a Name for the rule.
  6. Specify the following settings to match your web traffic:
    • Source – The source addresses of the traffic.
    • Service – Select HTTP+S.
    • Destination – Select Internet.
    • Connection Method – Select Dynamic SNAT.
    Google_accounts_02.png
  7. Click on the Application Policy link and select:
    • Application Control – Required.
    • SSL Interception – Required, since Google services are available exclusively via HTTPS.
    • Google Accounts – Required.
      Google_accounts_03.png
  8. (optional) Set additional matching criteria:
  9. Click OK.
  10. Place the access rule via drag-and-drop in the ruleset, so that no access rule above it matches this traffic.
  11. Click Send Changes and Activate.

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 CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > Firewall > Forwarding Rules.
  2. Click Lock.
  3. Either click the plus icon (+) at the top right of the ruleset, or right-click the ruleset and select New > Rule.
    FW_Rule_Add01.png
  4. Select Block as the action.
  5. Enter a Name for the rule.
  6. Specify the following settings to match your web traffic:
    • Source – The source addresses of the traffic. Use the same source as the access rule in step 2.
    • Service – Create and select the service object for UDP 443. For more information, see Service Objects.
    • Destination – Select Internet.
    Google_accounts_05.png
  7. (optional) Set additional matching criteria:
    • Authenticated User – Use the same user object as in step 2.
    • Schedule Object – Use the same schedule object as in step 2.
  8. Click OK.
  9. Place the access rule via drag-and-drop before the rule created in step 2.
  10. Click Send Changes and Activate.

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.

Google_accounts_04.png

Last updated on