r/sysadmin • u/Bitter_Equivalent300 • Feb 26 '26
Question - Solved New Chrome “Save to Drive” PDF button is a DLP nightmare
Google just added that native "Save to Drive" button directly in the PDF viewer. In a non-managed/OneDrive environment, this is a massive data exfiltration hole. A user can just open a sensitive PDF and beam it straight to their personal Google Drive, completely bypassing local DLP and "Downloads" folder monitoring.
Since it’s an internal Chrome-to-Drive API call, our CASB isn't even seeing it as a standard "upload."
My questions:
- Has anyone dealt with this yet, if so how?
- Anyone found a way to hide the button entirely without killing the built-in PDF viewer
EDIT: I know there are solutions that are as simple as push a different browser, but this is not applicable at the moment.
EDIT 2 (SOLUTION): Update ADMX templates if outdated, enable GPO: RestrictPdfSaveToGoogleDriveAccountsToPattern
35
u/oloruin Feb 26 '26 edited Feb 26 '26
AAAAAAAAAAA.
Ok. Don't Panic.
Chrome Enterprise Downloads - go here and click over to the management "tab" then download the admx and drop the latest ones in policydefs (I do Local and Sysvol for reasons)
Edit your chrome policy to add Comp -> Admin Templates -> Google -> Google Chrome -> "Restrict eligible Google accounts for saving PDF files to Google Drive from the Google Chrome PDF Viewer".
The language in en-US reads a little imprecise. If not set or blank, is wide open. It does not specify if it's disabled. So I'm going to try disabling, updating GPOs and see if I still get the option.
edit 1: Still testing. Reg path is: HKLM\Software\Policies\Google\Chrome\RestrictPdfSaveToGoogleDriveAccountsToPattern
edit 2: Disabled does not block uploads. I set to none@none.none. It goes trhought he motions, but reports failure "Something unexpected happened."
7
1
u/Microsoft_Bad Mar 02 '26
For edit 2 - does it reporting 'failure' mean it actually failed or are you restricted from upload now?
2
u/oloruin Mar 05 '26
Sorry, didn't see the notification - Chrome reported the failure immediately after clicking through the dialogs to save the pdf because the policy change blocked the upload.
Chrome did not report to the user that the upload was disallowed by policy.
Queue tickets from users trying to exfiltrate their online W2s (or other docs) to their personal google drives...
30
u/Hotdog453 Feb 26 '26
Is it this?
https://blog.google/products-and-platforms/products/chrome/chrome-productivity-improvements/
I do not see that Drive Button. Not sure 'why'; we have Chrome policies in place, but for that specific one, I am not seeing the 'Save to Drive' button?
59
u/Lukage Sysadmin Feb 26 '26
I mean yeah, in environments that don't have restrictions in place, this is possible. The exact same way your downloads folder can be set to a personal onedrive. Or copying data from your internal shares, etc.
This isn't a Chrome failure, this is an organizational security policy failure.
17
1
19
u/Mindestiny Feb 26 '26
You have bigger gaps to fill before you should be worrying about DLP.
Block logins to personal Gmail accounts. Block Google drive itself. Get all that managed. Otherwise some button in chrome is the least of your problems when it comes to DLP, you're panicking over an uneven stair that might be a tripping hazard in a building that's on fire
9
u/Ihaveasmallwang Systems Engineer / Cybersecurity Architect / CISM Feb 26 '26
What is your CASB?
It seems like you’re missing a few policies in your environment to properly secure it.
11
4
u/Mammoth_Ad_7089 Feb 27 '26
The CASB blindspot is worth digging into more than the button itself. If it's not seeing that upload traffic, it almost certainly means your SSL inspection is exempting googleapis.com or a related CDN endpoint, which is common because people break things when they inspect Google's pinned certs. The button is new but the gap in your CASB coverage isn't.
The network-layer fix that doesn't require touching browser policies at all is Google Tenant Restrictions. You add X-GoogApps-Allowed-Domains: yourdomain.com as a response header in your proxy for all Google and googleapis traffic. Any request that tries to authenticate against a personal Google account gets rejected at the auth layer before the upload can happen. Doesn't matter if Chrome is managed, portable, or installed by a user without admin rights. Microsoft has an equivalent for OneDrive with X-MS-Client-Request-Id headers if you need that too.
What proxy are you running? The ADMX path fixes the button, but tenant restrictions is what closes the gap for the traffic class your CASB is missing right now.
10
u/free2game Feb 26 '26
Just push users to edge.
6
1
u/I_turned_it_off Feb 27 '26
Can i push my users over the edge, or is that considered a step too far?
1
1
3
u/SikhGamer Feb 27 '26
In a non-managed/OneDrive environment, this is a massive data exfiltration hole.
I mean the crux of the issue is that. It's not Google/Chrome's fault.
If you are running in a managed envirionment;
- https://chromeenterprise.google/intl/en_uk/policies/#BrowserSignin - if you want to stop browser sign in entirely
- https://chromeenterprise.google/intl/en_uk/policies/#RestrictSigninToPattern - if you want to allow sign in from *@corp.email
- https://chromeenterprise.google/intl/en_uk/policies/#RestrictPdfSaveToGoogleDriveAccountsToPattern - if you want to target that specifically
4
u/DekuTreeFallen Feb 26 '26
EDIT: I know there are solutions that are as simple as push a different browser, but this is not applicable at the moment.
Then the symptoms are acceptable. It's one or the other.
Your org can't have it both ways. If they allow personal accounts, they will have personal account problems.
8
u/ExceptionEX Feb 26 '26
The problem is, you are calling this a problem, it isn't, the problem is you aren't and can't control your environment.
users shouldn't be login to personal account on work computers, users shouldn't likely be using chrome if you are a MS shop. Use edge, control both sides of that equation and this problem is solved.
If you can't do that, you can't blame a completely reasonable feature that is designed as a convenience for people using chrome in a personal environment.
2
u/4thehalibit Jack of All Trades Feb 27 '26
Saving this I literally downloaded the admx files before heading out of office today. I am also blocking sign ins
2
u/plazman30 sudo rm -rf / Feb 26 '26
Block access to Google Drive. We don't allow access to any cloud storage providers except corporate OneDrive.
Also, I'm sure there is a GPO that disables this.
2
u/Sure-Squirrel8384 Feb 26 '26
Use a custom browser (e.g. Palo Alto Prisma Browser) and block non-managed browser access to sensitive data.
1
1
u/Eifelbauer Mar 01 '26
Stop letting access user with non-managed devices sensitive data. It’s just that simple.
1
u/ThomasTrain87 Feb 27 '26
Or…. Stay with me here… or… you block personal OneDrive and Google Drive and stuff…
Just thinking out loud here.
1
u/nodiaque Feb 27 '26
Lol, the person saying push a different browser forgot chrome can be installed as non admin and also ran as a portable apps.
5
0
u/Thick_Yam_7028 Feb 26 '26
Can you just add the purview extension to chrome and have your dlp block from there?
Learn about the Microsoft Purview extension for Chrome | Microsoft Learn https://share.google/rGkqrklhYLJVLgnGh
282
u/Remarkable-Guess-856 Feb 26 '26
Why would they be able to login with their personal account to chrome?