{"id":299731,"date":"2025-04-06T05:59:27","date_gmt":"2025-04-06T12:59:27","guid":{"rendered":"https:\/\/sftarticles.wpenginepowered.com\/en\/?p=299731"},"modified":"2025-07-01T14:57:17","modified_gmt":"2025-07-01T21:57:17","slug":"how-gmails-end-to-end-encryption-works-for-enterprise-accounts","status":"publish","type":"post","link":"https:\/\/cms-articles.softonic.io\/en\/how-gmails-end-to-end-encryption-works-for-enterprise-accounts\/","title":{"rendered":"How Gmail\u2019s end-to-end encryption works for enterprise accounts"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Google is rolling out a&nbsp;<strong>new client-side encryption system for Gmail enterprise users<\/strong>, marking a significant step forward in email security and interoperability. This update introduces&nbsp;<strong>end-to-end encryption (E2EE)<\/strong>&nbsp;that works across different email platforms, including non-Gmail services, with user-controlled keys.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A simplified encryption method for greater compatibility<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unlike S\/MIME, which demands that users exchange and manage certificates,&nbsp;<strong>Google\u2019s new method removes that barrier by relying on client-side encryption<\/strong>. This means that emails are encrypted on the sender\u2019s device before being sent, and&nbsp;<strong>only the recipient can decrypt them<\/strong>, using their own access key.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Enterprise admins can now manage their own encryption keys, keeping&nbsp;<strong>data control firmly in the hands of the organization<\/strong>. This is a crucial shift for companies concerned about sensitive information being accessed by third-party providers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Encryption even beyond the Gmail ecosystem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This updated system allows&nbsp;<strong>secure communication with recipients outside the Gmail network<\/strong>. Gmail users will receive encrypted emails directly in their inbox, while non-Gmail recipients are redirected to a secure, read-only version of Gmail where they can view the message.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>For companies still using S\/MIME<\/strong>, Gmail will adapt by sending encrypted emails via that standard, ensuring backward compatibility.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">IT tools for greater protection<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google has introduced extra controls for IT teams, including the ability to&nbsp;<strong>enforce restricted Gmail viewing for external recipients<\/strong>\u2014even if they\u2019re Gmail users. This helps ensure that&nbsp;<strong>emails aren\u2019t stored on unmanaged devices or third-party servers<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, new features like client-side encryption defaults, data loss prevention tools, classification labels, and&nbsp;<strong>AI-powered spam and phishing protection<\/strong>&nbsp;are being integrated to strengthen security further.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google is rolling out a&nbsp;new client-side encryption system for Gmail enterprise users, marking a significant step forward in email security and interoperability. This update introduces&nbsp;end-to-end encryption (E2EE)&nbsp;that works across different email platforms, including non-Gmail services, with user-controlled keys. A simplified encryption method for greater compatibility Unlike S\/MIME, which demands that users exchange and manage certificates,&nbsp;Google\u2019s &hellip; <a href=\"https:\/\/cms-articles.softonic.io\/en\/how-gmails-end-to-end-encryption-works-for-enterprise-accounts\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;How Gmail\u2019s end-to-end encryption works for enterprise accounts&#8221;<\/span><\/a><\/p>\n","protected":false},"author":9317,"featured_media":299732,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wpcf-pageviews":0},"categories":[1015],"tags":[],"usertag":[],"vertical":[],"content-category":[],"class_list":["post-299731","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/299731","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/users\/9317"}],"replies":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/comments?post=299731"}],"version-history":[{"count":1,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/299731\/revisions"}],"predecessor-version":[{"id":308104,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/299731\/revisions\/308104"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/media\/299732"}],"wp:attachment":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/media?parent=299731"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/categories?post=299731"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/tags?post=299731"},{"taxonomy":"usertag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/usertag?post=299731"},{"taxonomy":"vertical","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/vertical?post=299731"},{"taxonomy":"content-category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/content-category?post=299731"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}