Google announced that it is introducing end-to-end encryption (E2EE) to Gmail on the web, allowing enrolled Google Workspace users to send and receive encrypted emails within and outside their domain.
Client-side encryption was already available for users of Google Drive, Google Docs, Sheets, Slides, Google Meet, and Google Calendar (beta).
Once enabled, Gmail client-side encryption will ensure that any sensitive data delivered as part of the email’s body and attachments (including inline images) cannot be decrypted by Google servers — the email header (including subject, timestamps, and recipients lists) will not be encrypted.
With Google Workspace Client-side encryption (CSE), content encryption is handled in the client’s browser before any data is transmitted or stored in Drive’s cloud-based storage. So Google servers can’t access your encryption keys and decrypt your data. After setting up CSE, you can select which users can create client-side encrypted content and share it internally or externally.
Gmail E2EE beta is currently available for Google Workspace Enterprise Plus, Education Plus, and Education Standard customers.
This feature is not yet available to users with personal Google Accounts or Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Education Fundamentals, Frontline, and Nonprofits, as well as legacy G Suite Basic and Business customers.
Google stated that Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between their facilities.
Comments