Reduce Data Leakage with Data Encryption in Google Drive
Pain Point
Sensitive customer data and creative content increasingly stored and shared using Google Drive. Risk of data leakage and unwanted sharing is deemed too great.
Company has been using Google Drive for a few years and all sorts of unstructured content is being uploaded to Google Drive by employees and partners.
Their IT department is interested in encrypting all content in Google Drive.
On-premise they have a solution for file-system encryption from Thales but that does not help with protecting the content moving to the cloud.
They want to bulk encrypt all user-generated content in Google Drive accounts in their domain to protect them from leaking in case of an account compromise.
However, they want to retain the ability to inspect encrypted files using their prevalent DLP solution. Users should not be able to upload/exfiltrate undesirable/sensitive content by employing encryption and thus making content opaque to DLP. Therefore, we needed to figure out how to allow the DLP solution to examine the file content in spite of encryption.
They have high employee turnover, so they want to ensure continuity access to their encrypted content even after an employee leaves the company.
The implementation to support their cloud-DLP solution with GarbleCloud is currently ongoing. Once testing is done, GarbleCloud will be rolled out for their 600 strong employee-base.