Google Meet

When a host starts or a participant joins an encrypted Google Meet session, the following "Wrap" process occurs:

Session Key Generation: Google generates a unique Session Encryption Key (acting as the DEK) for the meeting's media streams (audio and video).
Key Protection Request: Before the meeting starts, Google sends this session key to Oten KMS to be secured.
Key Wrapping: Oten KMS verifies the organizer's credentials and wraps (encrypts) the session key using the designated Customer Managed Key (CMK).
Key Distribution: The wrapped session key is distributed to authorized participants. Google servers facilitate the delivery but cannot decrypt the key.
Secure Handshake: Each participant's client sends the wrapped key back to Oten KMS (via the KACLS) to unwrap it using their own identity.
End-to-End Encryption: Once unwrapped, the session key stays in the browser's volatile memory to encrypt outgoing media and decrypt incoming media from other participants.

To optimize the use of this features across browsers and mobile apps, please configure your settings as follows:
- For mobile app:
  - Update the related apps to the latest version for the best experience (example: Gmail is 6.0.260406).
  - Chrome is the recommended default browser.
  - Android: If it does not work properly in the app, clear the cache and try again.
- For desktop app browser: Chrome (or Chromium core browser) is the recommended default browser.
These features work reliably in web browsers. On the mobile app, availability depends on the app version and Google's support, so usage may vary by version and is not always consistent.

Service

Apps

Data that's client-side encrypted

Data that's not client-side encrypted

Google Meet

Note:

Any data other than audio and video streams and chat messages

Last updated 2 months ago