I haven't tested this myself but you could try the following :
If I'm not mistaken for corporate Gmail access, the usernames have the customer domain name (eg. email@example.com).
Personal Gmail accounts have usual usernames (eg. firstname.lastname@example.org)
To block personal gmail access, enable ssl-decryption. Next, create a data pattern matching "@gmail.com".
Match this Data pattern on gmail-base app in a Data filtering object.
Apply the Data Filtering object to a policy.
This way you should be able to access corporate gmail accounts and personal gmail access should be blocked.
One caveat I think exists here :
Matching for the regex "@gmail\.com" in the whole page content might also have unwanted matches such as :
-Sending an email to email@example.com from the corporate account
-Reading an email from firstname.lastname@example.org on the corporate account
I would think along those lines ... other tips are welcome ^_^
Thanks for the idea, Kiwi.
Trying to test/implement it, but I think the problem is that there is no option to add ssl or google-base as application in Data filtering profile(whys is that?). Authentication form for gmail is done through accounts.google.com and its not detected as gmail-base application. Will continue testing. If anyone else have any ideas feel free to wite them here.
Step 1 Make sure you are decrypting traffic from the inside to the outside
Step 2 Create a custom URL with *.google.com and *.gmail.com
Step 3 Create a URL FILTER
Select HTTP HEADER Insertion
Called it GMAIL-GOOGLE Type Google apps Access control
Under domain add the following *.google.com and gmail.com
Select header X-GooApps-Allowed domain
Under value add your corporate domain example.com paloaltonetworks.com etc
You can add 5 domains
STEP 4 create a policy
INSIDE-2-OUTSIDE Inside outside APPS GOOGLE-APPS service URL Category=GMAIL-COORPORATE Action= allow profile=url Filtering =GMAIL-FILTER
GOOGLE-APPS= GMAIL, Google-BASE, ssl, RTCP,rtp-base,stun,web-browsing vidyo
Group.. i would recommend that the customer look at HTTP Header Insertion n under the URL Filter Profile section
With the HTTP header insertion and modification feature, you can now manage HTTP header information to disallow SaaS consumer accounts while allowing a specific enterprise account.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!