Google Workspace Client-side encryption is currently available for the following data: Regulatory compliance-Your organization operates in a highly regulated industry, like aerospace and defense, financial services, or government.Privacy-Your organization works with extremely sensitive intellectual property.Your organization might need to use CSE for various reasons-for example: This additional control can help you strengthen the confidentiality of your sensitive or regulated data. Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between its facilities. With CSE, however, you have direct control of encryption keys and the identity provider used to access those keys. Your users can share CSE files internally or with external organizations, if those organizations also use Google Workspace and set up CSE. To use CSE, you'll need to connect Google Workspace to an external encryption key service and an identity provider (IdP). That way, Google servers can't access your encryption keys and decrypt your data. With Google Workspace Client-side encryption (CSE), content encryption is handled in the client's browser before any data is transmitted or stored in Drive's cloud-based storage.
You can use your own encryption keys to encrypt your organization's data, in addition to using the default encryption that Google Workspace provides. Supported editions for this feature: Enterprise Education Standard and Education Plus.
0 kommentar(er)
