> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/rare-dlp-rule-match-by-user.md).
# Rare DLP rule match by user
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------ |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Office 365 Audit |
| Detection Modules | Identity Threat Module, SaaS Threat Detection, Email |
| Detector Tags | O365 DLP Analytics |
| ATT\&CK Tactic | Collection (TA0009) |
| ATT\&CK Technique | Data from Information Repositories: Sharepoint (T1213.002), Data from Information Repositories (T1213) |
| Severity | Informational |
### Description
A user triggered an O365 DLP rule match, which may indicate an attacker's attempt to access sensitive information.
### Attacker's Goals
An attacker is attempting to access sensitive information.
### Investigative actions
* Review the details of the triggered DLP rule match. Look for signs that the user account and mailbox are compromised (e.g. abnormal logins, unusual activity).
* Follow further actions done by the account.
* Communicate with the user to verify the legitimacy of the triggered event.
### Variations
DLP rule match by user for the first time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------ |
| ATT\&CK Tactic | Collection (TA0009) |
| ATT\&CK Technique | Data from Information Repositories: Sharepoint (T1213.002), Data from Information Repositories (T1213) |
| Severity | Low |
**Description**
A user triggered an O365 DLP rule match, which may indicate an attacker's attempt to access sensitive information.
**Attacker's Goals**
An attacker is attempting to access sensitive information.
**Investigative actions**
* Review the details of the triggered DLP rule match. Look for signs that the user account and mailbox are compromised (e.g. abnormal logins, unusual activity).
* Follow further actions done by the account.
* Communicate with the user to verify the legitimacy of the triggered event.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/rare-dlp-rule-match-by-user.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.