Microsoft’s DLP is probably one of those products that many people have heard about. Some might even know it can solve their organization’s issues, but do not know where to start. Hopefully, the following can assist in getting DLP going in your organization. The focus will be on the Office 365 DLP and not the on-premises implementations.
This article is accurate as of the date published. However, things move quickly in this space; features, availability, and coverage will change.
“Data loss prevention (DLP) helps you protect sensitive information and prevent its inadvertent disclosure. Examples of sensitive information that you might want to prevent from leaking outside your organization include financial data or personally identifiable information (PII) such as credit card numbers, social security numbers, or health records. With a data loss prevention (DLP) policy, you can identify, monitor, and automatically protect sensitive information across Office 365.”
DLP is an essential tool in today’s digital world. Users have multiple devices and want to have connectivity at all times. Implementing DLP will increase visibility into the organization information, files, the flow of information and the methodologies used by users when sharing this information.
The take away from Microsoft’s description of what DLP is should be the last sentence: “identify, monitor and automatically protect sensitive information across Office 365.” DLP is part of E3 and E5 licenses suites which most enterprises either already have or are planning on utilizing.
*One thing to point out is that Exchange Hybrid does not apply DLP to emails sent from on-premises user to on-premises user because the emails never leave the on-premises Exchange environment.
Now, don’t be discouraged if DLP doesn’t stretch across your entire application portfolio. If your users take advantage of OneDrive for Business and/or SharePoint Online as the primary means to either store and or share files you are as they say, “Golden.”
Let’s think about another use case. Many users email files as attachments, routinely. Good thing DLP protects Exchange Online!
Getting started with DLP is simple. You can start by establishing a DLP policy. Microsoft provides policy templates, that include HIPAA, U.S. PII, PCI-DSS, etc. You want to add a condition to a template policy? No problem, you can use labels as a condition to a policy.
Microsoft has thought of this and provides several ways to test without causing the help desk a flood of calls. It’s aptly called test mode. Test mode is accomplished by activating a simple option at the end of the policy creation, “I’d like to test it out first.” This option will also allow you to go from idea to research phase and to proof of concept quickly.
DLP reports will provide insights and allow you to tier certain critical policies to trigger emails notifications to both Global Admins and/or the offending user. In addition to notifications, content can also be blocked.
Microsoft understands that the IT department may not have (or want) ultimate responsibility of areas that implicate sensitive HR or government regulations that have the potential to become legal matters. Something like an organization’s security and compliance team may be the preferred administrators of DLP. The recommend approach is to create a security group and assign the appropriate permissions. This approach allows members to create and apply DLP policies, and not need access to the content being protected.
One of the best methods to prove to your managers, CIO, CTO, etc. that the protection DLP provides brings a lot of value and is worth investing the time and/or monies in is by providing reports generated during Test-Mode and invite them to a quick 30-minute demo. Ensure that the demo is based on a hypothetical data-loss scenario. What demonstrates more value than proof? By doing this, you can prove that if the policy you created was being enforced you could have prevented X from happening.
Additionally, the fact that you could test without unintended consequences provides value by removing the fear of a bad reputation for the IT department during a deployment of a new project.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
|cookielawinfo-checbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.