Set up Inline DLP for Gmail
IMPORTANT: Before setting up Gmail Inline DLP, you must open a support ticket, and request assistance in pre-configuring your tenant.
Step 1: Create a Gmail Instance in Skyhigh CASB
- Log in to Skyhigh CASB.
- Go to Settings > Service Management.
- Click Add Service Instance.
- Select Gmail, enter a name for this new instance, and click Done.
- To configure the instance, click Configure.
- Activate the Data Loss Prevention (DLP) to ensure compliance checkbox, and under Email DLP Mode, select Inline Only.
- Review the prerequisites, and activate I have reviewed all prerequisites checkbox.
- Make sure the following are complete:
- Domains. Populate with all public domains configured with the Google Suite tenant.
- Take a note of the Skyhigh CASB Email Service Domain. You will need this later.
- Select the checkbox confirming you've configured Gmail, as you need this in the next step.
- Review the settings, and click Done.
Step 2: Configure Gmail to Route Email to Skyhigh CASB
- Log in to Google Suite admin (https://admin.google.com), and go to Apps.
- Select Google Workspace.
- Select Gmail.
- Scroll down and select Hosts.
- On the Hosts tab, click ADD ROUTE.
- Enter the following details for the new mail route:
- Enter a name.
- Enter the single host as captured earlier (Skyhigh CASB Email Service Domain).
- Enter port 25.
- Disable MX lookup and Require secure transport TLS.
NOTE: Do not enable Require secure transport (TLS) because it requires communication between the email servers initiated with TLS. Skyhigh CASB uses START-TLS instead, which initiates communication with standard SMTP. Then upgrade to TLS after the connection is set up.
- Select the Settings for Gmail tab, and click Compliance.
-
Under the Content compliance section, click CONFIGURE .
- Configure the rule as follows:
- Enter a name for the rule (for example, Skyhigh CASB DLP).
- Select Outbound.
- Select Internal - sending to enable scanning for internal emails, sent from GMail to the Skyhigh CASB PoP. Click ADD.
- Advanced content match. Full headers, Not contains text, "X-SHN-DLP-SCAN: success".
- Change Route and select the host created earlier.
- More options:
- Select Users and Groups as the account type to affect.
- IMPORTANT: If this is a production environment, apply this rule to a test user/group so all mailboxes are not impacted.
IMPORTANT: Do not save the configuration yet.
- To enable DLP for specific users or mail groups, configure the following:
- Under Envelope filter, select Only affect specific envelope senders.
- Select Group membership (only sent mail) to enable DLP for mail groups.
- Click Select groups, and select the required mail groups.
- Click Save.
- Under Envelope filter, select Only affect specific envelope senders.
- Under the Settings for Gmail, select Routing.
- Find the SMTP relay service and click CONFIGURE.
- Configure the SMTP relay service rule as follows:
- Enter a name for the rule (for example, Skyhigh CASB DLP).
- Allowed Senders. Set to Only addresses in my domains.
- Authentication. Select Only accept mail from the specified IP addresses and enter the following based on the environment.
- You must add each IP address to the list as in the following Gmail rule:
Skyhigh CASB Source IP Addresses
|
- Encryption: Set Require TLS encryption and click SAVE.
- Once saved, you can view the compliance and SMTP relay configurations.
- Under the Settings for Gmail tab, select Spam, Phishing and Malware.
- Under Email allowlist, click the Edit icon.
- Add the IP addresses that were added in the Step 12 based on your environment separated by commas.
- Click SAVE.
- Once saved, you can view the following message.
Step 3: Configure a DLP Rule
- In Skyhigh CASB, go to Policy> DLP Policies, and add a new rule applied to Gmail. An example is shown below.
NOTE: The only actions supported are Generate Incident or Block Email.
Step 4: Test the Configuration
- Log in to Gmail using a user account, and send an email with content that will trigger the configured DLP rule.
- Confirm that the email is NOT received by the recipient.
- Confirm that a policy incident is created and the action blocked the email.