Security Insights · Cloud security · 8 min read
Is Google Drive Secure? Encryption, Keys and Sharing Explained
Is Google Drive secure? What Google encrypts, who holds the keys, what Workspace client-side encryption changes, and the Drive sharing settings to check.
Google Drive is where many people and organizations keep their everyday files. When they include contracts, HR records or client documents, someone asks whether Drive is secure enough, and the answer depends on what you need protection from.
This guide explains how Google encrypts Drive files, who holds the keys, what Workspace client-side encryption changes, and which sharing settings to check.
Is Google Drive secure?
For most everyday work, yes. Google Drive encrypts files in transit and at rest with AES-256, and supports 2-Step Verification, passkeys and detailed sharing controls. The caveat: by default Google manages the encryption keys and its systems decrypt files to run the service, so for highly sensitive files the question is who can decrypt.
How Google Drive encrypts files
In transit. Google's Workspace security help page says Google forces HTTPS for all transmissions between users and Google Workspace services, with perfect forward secrecy, and Google's Workspace encryption whitepaper says data is always encrypted when it moves between its data centers.
At rest. Google's Drive help page on encrypted files says all files uploaded to Drive or created in Docs, Sheets and Slides are encrypted in transit and at rest with AES-256 (our AES-256 guide explains the cipher), and the security help page lists file metadata such as titles and comments as encrypted at rest too. The whitepaper, dated June 2021, adds that each chunk of data gets its own key, which is encrypted again by a wrapping key managed by Google's key management service.
Who holds the keys?
Google does. The whitepaper says that in the default mode, Google manages cryptographic keys on behalf of its customers. When you open a file, Google's systems unwrap the chunk keys, decrypt the data in memory and return it to you over an encrypted connection.
This means someone who obtains the storage equipment can't read the data, because they don't have the keys. The whitepaper also says access controls ensure each chunk can only be decrypted by authorized Google services and employees, and access to the key service is restricted and logged. That suits everyday work, but for highly sensitive files it means Google's systems can decrypt them.
For Google Workspace, Google says customers own their data, and its privacy help page says Google may only access data in your account in strict compliance with its Privacy Policy and your Customer Agreement, and doesn't use Workspace data for advertising or sell it to third parties. On some editions, Access Transparency logs show admins what Google staff do with content.
What client-side encryption changes
Google Workspace client-side encryption (CSE) adds a layer on top of the default encryption. At the time of writing (November 2026), Google lists it for the Frontline Plus, Enterprise Plus, Education Standard and Education Plus editions. Files are encrypted in the browser before any data is sent to Google, with keys from an external key service your organization sets up, and your identity provider verifies users first. Google says its servers and third parties can't access your encryption keys and decrypt your data, so CSE does change who can decrypt. CSE doesn't cover the file title, metadata such as owner and last-modified time, or Drive labels.
The trade-offs Google documents
- Collaboration. Several people can edit an encrypted file, but not in real time. Suggestions in Google Docs and the Commenter permission aren't supported.
- Scanning. Google's CSE FAQ says encrypted files aren't scanned for phishing and malware, and data loss prevention scans can't read them, because Google's servers don't have access to the content.
- Running the keys. The whitepaper says key service or identity provider downtime temporarily blocks access, and Google's key service guide warns that if you switch a key service's URL to a different service, files encrypted with the old one can't be decrypted.
Personal Google Accounts and Google Workspace
The default encryption applies to personal and work accounts alike. The Google Drive terms of service say your content remains yours and files in your individual drive are private until you decide to share them. They also say Google may review content to determine whether it is illegal or violates its program policies, though that doesn't necessarily mean it reviews content.
A personal account relies mostly on sign-in security. 2-Step Verification adds a second step in case your password is stolen, and Google describes passkeys as more secure against phishing. For people at high risk of targeted attacks, Google recommends the Advanced Protection Program, which requires a passkey or security key to sign in and limits third-party app access to your data.
Workspace admins can enforce 2-Step Verification, including a security-key-only option, and Google is enforcing it for administrator accounts. Client-side encryption needs a Workspace account and an admin who turns it on.
The practical risk: sharing links and settings
Encryption doesn't help once a file reaches the wrong person, so sharing settings are the main practical risk. Google's guide to sharing in Drive says that with Anyone with the link, anyone on the internet who has the link can open the file without signing in to a Google Account. With Restricted, only people who have been given access can open it. For sensitive files, the same guide lets you:
- Keep general access on Restricted and share with named people as Viewer, Commenter or Editor.
- Limit who can download, print and copy the file, and stop editors from changing permissions and sharing.
- Add an access expiration date, up to a year ahead, for each person you share with. Google says this is available for work and school accounts.
In Google Workspace, admins can turn off sharing outside the organization, or limit it by warning users before they share, blocking link sharing or allowing only trusted domains. On Enterprise Standard and Plus and some other editions, trust rules give finer control over who users can share with, and data loss prevention for Drive can block or warn on external sharing of sensitive content, or disable download, print and copy.
Google Drive security features compared
Each protection answers a different threat. The last column is what matters for sensitive files.
| Protection | What it protects against | What it doesn't change (who can decrypt) |
|---|---|---|
| HTTPS in transit | Interception on the network | Google receives the file and can decrypt it |
| AES-256 at rest | Stolen disks and storage equipment | Google manages the keys by default |
| 2-Step Verification, passkeys and Advanced Protection | Sign-ins with a stolen password, and phishing | Who holds the keys |
| Sharing controls | Oversharing, open links and unwanted downloads | Recipients and Google's systems can still read the file |
| Trust rules and data loss prevention (Workspace) | Sharing with the wrong people, and sensitive content leaving the organization | Google's systems still read the content |
| Access Transparency (Workspace) | Google staff access to content without a record you can review | It records access; it doesn't prevent decryption |
| Client-side encryption (Workspace) | Google's servers and third parties reading file content | It changes who can decrypt, but limits co-editing and scanning, and doesn't cover titles |
Is Google Drive secure enough for government and regulated data?
Google's IRAP page says an independent third-party assessor evaluated Google Cloud and Google Workspace against OFFICIAL and PROTECTED controls from the Information Security Manual and found both strongly aligned with PROTECTED level control requirements, with Google Drive among the products in scope. Reports can be requested through Google's Compliance Reports Manager, and our guide to the IRAP assessment explains what that involves.
Workspace data regions let admins on supported editions keep covered data, including original file content uploaded to Drive, in the United States or Europe.
An assessment confirms that controls are in place; it doesn't change who holds the keys. For legal privilege, health records or investigation material, the narrower question is whether the provider should be able to read the file at all. If not, the options are client-side encryption, with its trade-offs, or a service built on zero-knowledge encryption, where files are encrypted end to end before they leave the device.
Where DekkoCORE fits
A practical approach is to keep Google Workspace for everyday work and use DekkoCORE for the most sensitive files and external exchanges, where the provider must not be able to read the content. Files are encrypted on the user's device with AES-256 keys before they're uploaded, and every file has its own key. DekkoCORE stores only ciphertext and never has the keys to open files, so not even DekkoSecure can read them. Keys are handled automatically in the background, with no HSMs, key servers or key ceremonies.
DekkoCORE is a standalone platform, not an add-on to another storage service. Shares can have expiry dates and be revoked instantly, and External Members see only the folders shared with them. DekkoCORE is IRAP assessed to PROTECTED, and customers choose hosting in Australia, the United States or Canada. Our guide to secure file sharing covers the wider options.
Common questions
Frequently Asked Questions
Is Google Drive safe for confidential documents?
For most business documents, its encryption, sign-in protections and sharing controls are substantial protection. For files the provider must not be able to read, remember that Google manages the keys unless you use Workspace client-side encryption.
Is Google Drive encrypted?
Yes. Google says files uploaded to Drive or created in Docs, Sheets and Slides are encrypted in transit and at rest with AES-256. Google manages those keys by default.
Is Google Drive end-to-end encrypted?
Not by default. Standard Drive encryption uses keys Google manages, so Google's systems can decrypt files. Workspace client-side encryption encrypts files in the browser with keys your organization controls, which Google says its servers can't access.
Can Google see my Google Drive files?
By default, Google's systems hold the keys and decrypt files to provide the service. For Workspace, Google says it may only access your data in strict compliance with its Privacy Policy and your Customer Agreement. With client-side encryption, Google's servers don't have access to file content.
Are "Anyone with the link" files safe?
Anyone on the internet who has the link can open the file without signing in to a Google Account. For sensitive files, keep general access Restricted, share with named people and, on work or school accounts, add an expiration date.