{"id":11770,"date":"2023-03-01T20:54:09","date_gmt":"2023-03-01T19:54:09","guid":{"rendered":"http:\/\/plus.maciejpiasecki.info\/index.php\/2023\/03\/01\/client-side-encryption-rolling-out-for-all-eligible-gmail-users\/"},"modified":"2023-03-01T22:58:55","modified_gmt":"2023-03-01T21:58:55","slug":"client-side-encryption-rolling-out-for-all-eligible-gmail-users","status":"publish","type":"post","link":"https:\/\/plus.maciejpiasecki.info\/index.php\/2023\/03\/01\/client-side-encryption-rolling-out-for-all-eligible-gmail-users\/","title":{"rendered":"Client-side encryption rolling out for all eligible Gmail users"},"content":{"rendered":"

Google is widely rolling out client-side encryption (CSE) for Gmail. The new privacy feature is available for all organizations on a Google Workspace Enterprise Plus, Education Plus, or Education Standard plan. Users with personal Google accounts or on other Workspace plans aren\u2019t getting it, at least not just yet.
\nGoogle has been testing CSE for Gmail for the past few months. It released the feature in beta for users on the aforementioned three Workspace plans in December last year. This came after the company rolled out CSE widely for Google Drive, Google Docs, Sheets, Slides, and Google Meet. The tech biggie also expanded the privacy feature to Google Calendar a couple of weeks back. Eligible Gmail users are now getting it as well.
\nCSE adds another layer of protection to Google\u2019s already secure Workspace service. As the company explains, \u201cWorkspace already\u00a0encrypts data at rest and in transit by using secure-by-design cryptographic libraries\u201d. But with CSE, customers have \u201csole control\u201d over their encryption keys and the identity service to access those keys. The email body and attachments are indecipherable to Google servers as well as other external entities. Google says this gives customers \u201ccomplete control over access to their data.\u201d
\nGoogle brings client-side encryption to all eligible Gmail users
\nClient-side encryption gives \u201corganizations higher confidence that any third party, including Google and foreign governments, cannot access their confidential data,\u201d Google wrote in a blog post announcing the general availability of CSE for Gmail. The feature is already available for all eligible users irrespective of whether they are on Rapid Release or Scheduled Release domain. However, it isn\u2019t enabled by default. Admins have to manually enable it at the domain, OU, and Group levels. This can be done by going to Admin console > Security > Access and data control > Client-side encryption.
\nOnce CSE is enabled by your Workspace admin, you can add client-side encryption to any email by clicking the lock icon at the right end of the \u201cTo\u201d field. Here, you can \u201cTurn on\u201d Additional encryption and you\u2019re good to go. You can then proceed to compose your message and add attachments as you normally do. Google will take care of the rest. The company says that the experience will not change for users who were already taking advantage of this feature in beta. For everyone else, these few extra clicks will greatly elevate the security of your email and attachments.<\/p>\n

The post Client-side encryption rolling out for all eligible Gmail users appeared first on Android Headlines.
\n
\nSource: ndroidheadlines.com <\/p>\n","protected":false},"excerpt":{"rendered":"

Google is widely rolling out client-side encryption (CSE) for Gmail. The new privacy feature is available for all organizations on […]<\/p>\n","protected":false},"author":12,"featured_media":11771,"comment_status":"false","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11770","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bez-kategorii"],"_links":{"self":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/11770","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/comments?post=11770"}],"version-history":[{"count":1,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/11770\/revisions"}],"predecessor-version":[{"id":11772,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/11770\/revisions\/11772"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media\/11771"}],"wp:attachment":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media?parent=11770"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/categories?post=11770"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/tags?post=11770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}