Google has introduced encryption on client’s side in Gmail

Google announced the launch of the beta-version of the client’s beta (Client-Side Encryption, CSE), which allows users to send and receive encrypted emails in their domain and beyond.

Closing on the client side at Gmail will be available in the Beta version of the Google WorkSpace Enterprise customers Plus, Education Plus and Education Standard. Users can apply for beta testing until January 20, 2023. CSE is not available for Google personal accounts.

“The use of encryption on the client’s side in Gmail guarantees that confidential data in the body of writing and investments are not lended to deciphering Google servers. Clients retain control over encryption and identification service for access to these keys,” the terms google.

Google application for PC, Android and iOS already supports encryption on the client side. According to Google, this function will be integrated into MEET mobile applications and calendar in the next issue.

Closing on the side of the Client Google WorkSpace (CSE) allows you to encrypt the content in the client browser before the data is transferred or saved in the cloud vault of the disk. The company indicated that it could not access user encryption keys.

To add CSE to any message, you need to click on the castle icon and select “Additional encryption”

It is important to note that encryption on the client side (CSE) differs from through encryption (E2EE).

CHISTING on the client side allows organizations to encrypt data using their own cryptographic keys. Data is deciphered on the client’s side using the keys that are generated and controlled by the cloud key management service .

.

This means that the data is protected from unauthorized access even from the server or service provider. However, the organization or administrator have control over the keys and can track encrypted user files or cancel the user access to the keys, even if they were generated by the user himself.

And with end -to -end encryption, the information is encrypted on the sender of the sender and can be deciphered only on the device of the recipient using the key known only to the sender and recipient.

/Media reports cited above.