Connect Microsoft Exchange and Enterprise DLP

1. Contact your email domain provider to update your SPF record to add the required Enterprise DLP service IP addresses.

   Add the IP addresses for the region where you host your email domain. You can update your SPF record with multiple regional IP addresses if you have email domains hosted in multiple regions.

   • APAC
     35.186.151.226 and 34.87.43.120
   • Australia
     35.197.179.113 and 35.244.122.65
   • Europe
     34.141.90.172 and 34.107.47.119
   • India
     34.93.185.212 and 35.200.159.173
   • Japan
     34.84.8.170 and 35.221.111.27
   • United Kingdom
     34.105.128.121 and 34.89.40.221
   • United States
     34.168.197.200 and 34.83.143.116
2. Add a DNS TXT record to your email domain to validate email domain ownership when onboarding the domain to Email DLP.

   Enterprise DLP validates email domain ownership by requiring you to add a unique, system-generated token to your email domain's DNS TXT records. Enterprise DLP then performs a DNS lookup to verify this token, ensuring only authorized administrators can onboard email domains to Email DLP to prevent domain spoofing.

   You can add a DNS TXT record for a Microsoft Exchange email domain or you can connect a DNS TXT record at any third party domain provider.

   Repeat this step for all email domains you plan to onboard to Email DLP.

   Enterprise DLP doesn't require domain validation if:

   • The parent domain of a subdomain was already verified.
     For example, you have already onboarded the parent domain acme.com and Enterprise DLP successfully validated it. In this case, validation of the support.acme.com subdomain isn't required.
   • You removed and re-added an onboarded domain within the last 90 days. Enterprise DLP stores domain validation records for all onboarded domains for up to 90 days.
     For example, you onboarded the acme.com domain and Enterprise DLP successfully validated it. On August 1st, you removed the domain from Email DLP. On September 19th, you added it back to Email DLP. In this case, Enterprise DLP doesn't need to validate the domain again because the domain validation records for the acme.com domain are still stored.
3. Review the Email DLP setup prerequisites and allow the Email DLP egress IP addresses and outbound SMTP server domains on your organization's inbound SMTP server to receive delivery notifications.
4. (Best Practices) Confirm you configured Active Directory correctly so that email senders have a manager to approve or reject quarantined emails.

   Email DLP requires Microsoft Exchange Active Directory to assign a manager to a sender. You can create a transport rule to quarantine and send the email for approval by the sender's manager. A sender must have a manager assigned to successfully quarantine a sender's email if Enterprise DLP detects sensitive data.

   If you did not assign a manager to a user, then Microsoft Exchange sends the quarantined email to the intended recipient. Microsoft Exchange requires that you assign a user a manager to approve or reject the email.
5. (Best Practices) Save Evidence for Investigative Analysis with Enterprise DLP.

   Palo Alto Networks recommends configuring evidence storage so you can download emails for investigative analysis when you review Email DLP incidents.
6. Set up the Cloud Identity Engine (CIE).

   Palo Alto Networks recommends using CIE so you can create targeted Email DLP policy rules.
7. Create the Microsoft Exchange connectors and transport rules, and create the Email DLP Policy.

   Palo Alto Networks recommends setting up all connectors, transport rules, and Email DLP policy rules to ensure enforcement begins as soon as you successfully connect Microsoft Exchange Online to Enterprise DLP.

   • Create a Microsoft Exchange Outbound Connector
     The outbound connector controls the flow of emails forwarded from Microsoft Exchange to Enterprise DLP.
   • Create a Microsoft Exchange Inbound Connector
     The inbound connector controls the flow of emails forwarded to Enterprise DLP back to Microsoft Exchange.
   • Create Microsoft Exchange Transport Rules
     Transport rules allow Microsoft Exchange to forward emails to Enterprise DLP and specify the actions Microsoft Exchange takes based on the hosted quarantine, admin approval, manager approval, encrypt, or block transport rules verdicts rendered by Enterprise DLP.
   • Add an Enterprise DLP Email Policy
     The Email DLP policy specifies the incident severity and the action Enterprise DLP takes when matching traffic is inspected and sensitive data is detected.
8. Obtain Your Microsoft Exchange Domain and Relay Host.
9. Log in to Strata Cloud Manager.
10. Select ConfigurationSaaS SecuritySettingsApps Onboarding.
11. Search for Exchange and click Microsoft Exchange.

12. In the Email DLP Instance, click Add Instance.
13. In the Setup Connectors and Rules page, click Continue to Next Section since you have already configured the outbound connector, inbound connector, and transport rules.
14. Configure one or more email domains.

    Enterprise DLP requires adding one or more email domains and relay hosts to ensure Enterprise DLP can successfully forward inspected emails back to Microsoft Exchange.

    1. (Optional) Enable Custom Routing.

       If you have a complex multivendor email security chain, enabling custom routing enables Email DLP to scan emails within complex multivendor email security chains while maintaining your existing infrastructure. Custom routing also helps prevent sender spoofing through IP validation.
    2. Enter an Email Domain, its corresponding Relay Host, and the networking Port.

       Obtain Your Microsoft Exchange Domain and Relay Host if you don't have the Microsoft Exchange email domain and relay host immediately available.

       (Custom Routing) If you enabled custom routing, enter the relay domain of the next hop server.
    3. (Optional) Click Add Domain for any additional email domains.
    4. Connect.
15. (Custom Routing only) For the Source IP Allow List, enter a trusted SMTP traffic source forwarding emails to Enterprise DLP.

    Enterprise DLP supports static IPv4 addresses and Classless Inter-Domain Routing (CIDR) IP ranges. It takes up to 2 minutes for Email DLP to add domains and IP addresses to the email inspection flow when connecting Email DLP for the first time or editing an existing configuration.

    The Source IP Allow List restricts Enterprise DLP email acceptance to only those emails originating from your specified IP addresses or address ranges. This prevents spoofing attacks by rejecting emails that claim to be from your organization's domain but come from unauthorized mail servers.

    Click Add Source IP to add more trusted SMTP traffic sources. Email DLP supports up to 20 unique IP addresses and CIDR ranges.
16. Verify that Microsoft Exchange is successfully connected and onboarded.

    • Domain Validation Error
      This error message appears if the DNS TXT record for your email domain is missing or incorrect

17. Configure the Email DLP settings.

    • Edit the snippet settings to configure if and how Enterprise DLP stores and masks snippets of sensitive data that match your data pattern match criteria.
    • Edit the policy evaluation timeout settings to configure what Enterprise DLP does when Email DLP policy evaluation exceeds the configured timeout.
    • Configure evidence storage to save evidence for investigative analysis.