Enabling Content inspection on Google Translate

Products

• CASB Advanced Threat Protection
• CASB Audit
• CASB Gateway
• CASB Gateway Advanced
• CASB Security Advanced
• CASB Security Advanced IAAS
• CASB Security Premium
• CASB Security Premium IAAS
• CASB Security Standard
• CASB Securlet IAAS
• CASB Securlet SAAS
• CASB Securlet SAAS With DLP-CDS

Issue/Introduction

Google Translate is a service that is widely used for language translation. it is a cloud service where the "text" to be translated has to be sent externally for translation. this could leak some of the internal sensitive data to the wild.

CloudSoc Gateway services can be used to inspect and sanction the contents sent to Google Translate.

Environment

1- Cloudsoc Tenant with proper Gateway and Custom Gatelet licenses.

2- Scan Request payload is enabled (Login to Cloudsoc Console > Settings > Gateway > Under the "Scan Request Payload" , switch them on.

 

Resolution

1- Define a Custom Gatelet

Location: Store > Gatelets 'section' > click on "Create Custom Apps" > Enter a Display name > Select "scan Request Payload" > Under the "Domains" section Click on "Manual Entry" > Enter "translate.google.com"

The final screen will look like this

2- On DLP Enforce, configure a policy according to the business requirement, in this example a keyword policy will be used 

Note: using the "application detection" feature in DLP Enforce, the policy can be specified more to the custom Gatelet only.

3- If the end-user enters a keyword that violates the policy , the translation pan will show an error like this:

Additional Information

Keep in mind that Google offers the translation service on different places, one of them is the embedded objects on the landing page of Google's search. That one can be managed by Web Proxy or Endpoint controls.

Here is a ProxySG KB article on how to leverage the ProxySG capabilities to control that traffic