Created on
‎06-30-2025
03:28 AM
Edited on
‎09-01-2025
11:08 PM
By
Jean-Philippe_P
Description | This article describes how to block Google Drive when Deep Inspection and Application Control are not available. Controlling cloud services is challenging because Google services (Gmail, Docs, Drive) share IP ranges, making IP-based blocking impractical and disruptive. |
Scope | FortiGate. |
Solution |
Although the recommended method to block access to Google Drive or other Cloud Storage services is Application Control with Deep Inspection, a practical workaround is to restrict access using fully qualified domain names (FQDNs), including static and wildcard entries. This approach targets Google Drive more precisely without unintentionally blocking other essential Google services.
[Static FQDN]
googledrive.com
drive.google.com
drive.usercontent.google.com
drive-data-export.usercontent.google.com
drive-data-export-eu.usercontent.google.com
[Wildcard FQDN]
*.drive.google.com
Sample configuration for Firewall Addresses and Policies:
config firewall address
edit "GDRIVE"
set type fqdn
set fqdn "googledrive.com"
next
end
Note: The same configuration should be done for all static and wildcard FQDNs.
config firewall policy
edit 1
set name "Block_Drive"
set srcintf "port3"
set dstintf "virtual-wan-link"
set srcaddr "all"
set dstaddr "GDRIVE"
set schedule "always"
set service "ALL"
set logtraffic enable
set action deny
next
end
Static and wildcard FQDNs may change at any time by Google. For the latest updates, refer to the Google support page:
Important: Ensure DNS queries traverse the FortiGate when using wildcard FQDNs so it can cache resolutions and continuously refresh the wildcard FQDN object.
Related article:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.