Google is updating the client-side encryption mechanism for Google Meet to permit exterior members, together with these with out Google accounts, to hitch encrypted calls.
Consumer-side encryption ensures that solely folks within the assembly have entry to the info delivered by way of the applying.
Google Meet is a part of the Google Workspace suite and gives customers with safe video conferences and calls over the web. The app has over 5 billion downloads on Google Play.
Though Google had already carried out client-side encryption in Meet, the applying didn’t have the choice for exterior customers to hitch safe calls.
“Meet already encrypts all of your data at rest and in transit between our facilities — client-side encryption gives users direct control of their encryption keys and the identity service that they choose to authenticate for those keys,” reads Google’s announcement.
“Adding support for external participants means customers can collaborate with any of their stakeholders safe in the knowledge that only the meeting participants can decrypt the call media.”
Google began this week to roll out client-side encryption updates for Workspace prospects with Enterprise Plus, Training Commonplace, and Training Plus licenses.
To activate the function, admins need to replace their IdP/KACLS configurations to open up entry to exterior members and decide third-party identification suppliers that can be utilized to hitch the assembly.
Exterior customers invited to an encrypted Meet session have to first confirm their identification utilizing a technique supported by the third-party Id Supplier (IdP) configured by the assembly’s administrator.
Supported strategies embody utilizing an present Google or Microsoft account in addition to a one-time password equipped by way of SMS or e-mail.
Extra particulars for Meet Consumer-side Encryption (CSE) are obtainable right here. Admins can observe these directions to supply exterior members entry to client-side encrypted content material.
