Creating Scoped DLP rules with Custom Sensitive Information Types

Creating Scoped DLP rules with Custom Sensitive Information Types

5 / 5 ( 4 votes )

A few weeks ago, I put out a series of posts on creating and using custom sensitive information types (  The blog, posts, however, focus on using the DLP configuration options available in the Security & Compliance Center.

Rules created via the DLP wizard in the Security & Compliance Center have the benefit of being able to be applied globally across your organization and its content sources.  However, due to the global focus, you do lose some of the granularity in crafting rules.  Multi-organization tenants (such as enterprise conglomerates or consolidated governments) may need to create email DLP policies that are more restrictive and apply only to certain business units or agencies.

For this, we need to head to the Exchange Admin Center.

  1. First, build or import a custom DLP package (you can use mine, as outlined here) or build your own (as described here) and get them imported into Office 365.
  2. Navigate to the Exchange Admin Center ( | Compliance | Data Loss Prevention).
  3. Click + and select New custom DLP policy.
  4. Name the custom policy, select Test with policy tips and then click Save.
  5. Select the policy in the list, and then click the Edit (pencil icon) button.
  6. Select the Rules tab.
  7. Click + and select Create a new rule.
  8. Enter a name for the rule, and then select More options … at the bottom of the page to expose more configuration options for the rule.
  9. Select a method to identify senders.  For example, you can use text or pattern matches, domains, or additional properties.  In this example, I’m going to select Sender is a Member of a GroupNote: If you want to use “Notify the sender with a policy tip” action, you cannot select Sender Domain Is or Sender Address Matches Patterns as conditions.  You have to choose different selection criteria, such as “Inside Organization” or “Member of a group.”
  10. Select a group, and then click the Add to add it to the list of groups to be included as conditions of this rule.  Click OK when finished.
  11. Select the Add Condition button to add another condition to search for.
  12. Select The message … and then select contains any of these sensitive information types.
  13. On the Contains any of these sensitive information types page, click +.
  14. Select the custom sensitive information types from the list, and then click Add.
  15. Select OK to add the sensitive information types to the rule.
  16. Click OK to complete the rule conditions.
  17. Add one or more actions.  Recommended actions might be to Forward the message for approval to a manager, Encrypt, or Notify the sender with a Policy Tip.  In this example, I selected Notify the sender with a Policy Tip, and then selected Block the message, but allow the sender to override with a business justification and send.
  18. Add an NDR that users will receive if an override justification isn’t given and click OK.
  19. Select Add Action if any additional action is needed.  In this example, I’m going to select Modify the Message Security | Apply Office 365 Message Encryption and rights protection.
  20. Select a template and click OK.
  21. Add Exceptions, if any. I want to put the hammer down on folks, so no exceptions here.
  22. Select the mode for the rule.  I generally start Test with Policy Tips to start, and then move to Enforce after making sure it triggers appropriately.
  23. Under Match sender address in message, select Header or envelope, and then click Save.
  24. If you have chosen an action that has a potential to NDR, acknowledge by clicking OK.
  25. Click Save.
  26. Annnnd done.

Published by Aaron Guilmette

Helping companies conquer inferior technology since 1997. I spend my time developing and implementing technology solutions so people can spend less time with technology. Specialties: Active Directory and Exchange consulting and deployment, Virtualization, Disaster Recovery, Office 365, datacenter migration/consolidation, cheese. View all posts by Aaron Guilmette

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Exit mobile version