• Gmail users can now send and receive encrypted emails both inside and outside of their domain.
• End-to-end encryption (E2EE) was already available to users of Google Drive, Google Docs, Sheets, Slides, Google Meet, and Google Calendar.
• The feature will be turned off by default, but it can be turned on at the domain, organisational unit, and Group levels by going to Admin console.

End-to-end encryption (E2EE) to Gmail on the web means that users who have signed up for Google Workspace can now send and receive encrypted emails both inside and outside of their domain.

Once turned on, Gmail client-side encryption will make sure that not even the Google servers can decrypt any information sent as an attachment or as part of an email.

Client-side encryption, which Google calls E2EE, was already available to users of Google Drive, Google Docs, Sheets, Slides, Google Meet, and Google Calendar (beta).

Google said on its support website, “With Google Workspace Client-side encryption (CSE), content encryption is done in the client’s browser before any data is sent or stored in Drive’s cloud-based storage.”

“So, Google servers won’t be able to get to your encryption keys and read your encrypted data. After you set up CSE, you can choose which users can make client-side encrypted content and share it internally or externally.”

Users have until January 20, 2023, to apply for the beta by sending in their Gmail CSE Beta Test Application with their email address, Project ID, and test group domain.

Google Workspace Enterprise Plus, Education Plus, and Education Standard customers can use the Gmail E2EE beta right now.

The feature is not yet available to people with personal Google accounts or Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Education Fundamentals, Frontline, and nonprofits. This is also true for customers who already had G Suite Basic or Business.

After Google sends an email saying the account is ready, admins can set up Gmail CSE for their users by following the steps below to set up their environment, prepare S/MIME certificates for each user in the test group, and set up the key service and identity provider.

The feature will be turned off by default, but it can be turned on at the domain, organisational unit, and Group levels by going to Admin console > Security > Access and data control > Client-side encryption.

Once it’s turned on, you can turn on E2EE for any message by clicking the lock icon next to the Recipients field and clicking “Turn on” under “Additional encryption.”

Then you can write your Gmail message and attach files like you normally would.

“Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between our facilities,” Google said.

“Client-side encryption helps protect the privacy of your data and meets a wide range of requirements for data sovereignty and compliance.”

Also Read

Humanitarian disasters will be fueled by climate change in 2023

The number of people in need of humanitarian assistance has increased dramatically....