DLP Detections Test

To comply with business standards and industry regulations, organizations need to 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 in the Office 365 Security & Compliance Center, you can identify, monitor, and automatically protect sensitive information across Office 365.

A DLP policy contains a few basic things:

Where to protect the content - locations such as Exchange Online, SharePoint Online, and OneDrive for Business sites.
When and how to protect the content by enforcing rules comprised of:
- Conditions the content must match before the rule is enforced -- for example, look only for content containing Social Security numbers that's been shared with people outside your organization.
- Actions that you want the rule to take automatically when content matching the conditions is found -- for example, block access to the document and send both the user and compliance officer an email notification.

You can use a rule to meet a specific protection requirement, and then use a DLP policy to group together common protection requirements, such as all of the rules needed to comply with a specific regulation.

Whenever a DLP rule applied to Exchange Online is violated, an administrator should be instantly notified of the violation, with details of the rule/policy that was violated and the email sender/receiver who violated it. Administrators can easily and efficiently investigate DLP violations when they have access to this information. This is exactly the kind of assistance the DLP Detections test provides to administrators!

This test monitors the email traffic over Exchange Online, instantly captures traffic that violates any of the DLP rules that apply to the Exchange Online location, and promptly alerts administrators to such violations. Detailed diagnostics reported by the test provide the complete details of each violation, thereby enabling administrators to accurately identify the rules and policies that were violated, the emails that violated the rules and policies, and the senders and receivers responsible for the same. This information helps administrators investigate and take appropriate action against the violations.

Target of the test : Exchange Online

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the monitored Office 365 tenant

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured. By default, this is portal.office.com
Tenant Name	This parameter applies only if you want the eG agent to use Azure AD Certificate-based Authentication for accessing and monitoring an O365 tenant and its resources. Azure AD certificate-based authentication (CBA) enables customers to allow or require users to authenticate with X.509 certificates against their Azure Active Directory (Azure AD) for applications and browser sign-in. When monitoring highly secure Office 365 environments, you can configure the eG agent to identify itself to a tenant using a valid X.509 certificate, so that it is allowed secure access to the tenant and its resources. By default, the value of this parameter is none. This means that, by default, the eG agent does not use certificate-based authentication to connect to an O365 tenant. On the other hand, if you want the eG agent to use this modern authentication technique to securely access a tenant's resources, you should do the following: Enable Azure AD Certificate-based authentication for the target O365 tenant; this can be achieved manually, via the Office 365 portal, or automatically, using Powershell scripts we provide. For the manual procedure, refer to Manually Enabling Certificate-based Authentication For an Office 365 Tenantunder Microsoft Office 365. For the automatic procedure, refer to Automatically Fulfilling Pre-requisites in a Modern Authentication-Enabled Environmentunder Microsoft Office 365. When enabling certificate-based authentication, an X.509 certificate will be generated for the target tenant. Configure the Tenant Name parameter with the name of the tenant for which certificate-based authentication is enabled. Using the tenant name, the eG agent will be able to read the details of the X.509 certificate that is generated for that tenant, and use that certificate to access that tenant's resources. To determine the tenant name, do the following: Log in to the Microsoft 365 Admin Center as an administrator. Under Setup, click on Domains. Find a domain that ends with .onmicrosoft.com - this is your Microsoft O365 tenant name.
O365 User Name, O365 Password, and Confirm Password	These parameters need to be configured only if the Tenant Name parameter is set to none. On the other hand, if a valid Tenant Name is configured, then you should set these parameters to none . For execution, this test requires the privileges of an O365 user who is vested with the View-Only Audit Logs, View-Only Recipients, Mail Recipients, and Mailbox Import Export permissions. Configure the credentials of such a user against O365 User Name and O365 Password text boxes. Confirm the password by retyping it in the Confirm Password text box. While you can use the credentials of any existing O365 user with the afore-said privileges, it is recommended that you create a special user for monitoring purposes using the Office 365 portal and use the credentials of that user here. To know how to create a new user using the Office 365 portal and assign the required privileges to that user, refer to Creating a New User in the Office 365 Portal under Microsoft Office 365. You can also use eG's proprietary PowerShell script to automatically create a new user, or assign the required privileges to an existing user. To know how to use this script, refer to theAutomatically Fulfilling Pre-requisites in a Basic Authentication-Enabled Environmenttopic.
Domain, Domain User Name, Domain Password, and Confirm Password	These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server. In this case, in the Domain text box, specify the name of the Windows domain to which the eG agent host belongs. In the Domain User Name text box, mention the name of a valid domain user with login rights to the eG agent host. Provide the password of that user in the Domain Password text box and confirm that password by retyping it in the Confirm Password text box. On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of these parameters. By default, these parameters are set to none.
Proxy Host, Proxy Port, Proxy User Name, and Proxy Password	These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server. In this case, provide the IP/host name and port number of the Proxy server that the eG agent should use in the Proxy Host and Proxy Port parameters, respectively. If the Proxy server requires authentication, then specify the credentials of a valid Proxy user against the Proxy User Name and Proxy Password text boxes. Confirm that password by retyping it in the Confirm Password text box. If the Proxy server does not require authentication, then specify none against the Proxy User Name, Proxy Password, and Confirm Password text boxes. On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of any of the Proxy-related parameters. By default, these parameters are set to none.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time the test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
DLP detections	Indicates the number of DLP rules that were violated.	Number	Ideally, the value of this measure should be 0. A non-zero value implies that one/more DLP rules have been violated. In this case, you can use the detailed diagnosis of this measure to know which emails violated the rules, which rules were violated, which policies these rules belong to, and which senders and receivers violated them.
Unique senders	Indicates the number of unique senders who violated one/more DLP rules.	Number	Use the detailed diagnosis of this measure to know the senders of emails that violated a DLP rule.
Unique receivers	Indicates the number of unique receivers who violated one/more DLP rules.	Number	Use the detailed diagnosis of this measure to known who were the receivers of emails that violated one/more DLP rules.

The detailed diagnosis of the DLP detections measure reveals the details of those emails that violated one/more DLP rules. The subject of the email, the sender and receiver of the email, the date/time at which the email was sent, the rule that is violated, and the DLP policy that includes that rule are displayed as part of the detailed metrics. Using this information, administrators can easily investigate DLP violations.

Figure 1 : The detailed diagnosis of the DLP detections measure

To quickly identify all those email senders who violated one/more DLP rules, use the detailed diagnosis of the Unique senders measure.

Figure 2 : The detailed diagnosis of the Unique senders measure reported by the DLP Detections Test

To quickly identify all those email receivers who violated one/more DLP rules, use the detailed diagnosis of the Unique receivers measure.

Figure 3 : The detailed diagnosis of the Unique receivers measure reported by the DLP Detections Test