> For the complete documentation index, see [llms.txt](https://guides.mangoapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.mangoapps.com/admin-guide/compliance/dlp-policies/matches-log.md).

# Matches Log

### Overview

The Matches Log in Data Loss Prevention (DLP) Policies provides a comprehensive list of content containing sensitive information that has been matched based on the policy rules. 

<figure><img src="/files/9AtOmXtUjcuk3gdHBqF9" alt="" width="563"><figcaption></figcaption></figure>

This log helps administrators monitor and manage data security incidents.

***

### **Matches Log Dashboard Overview**

The Matches Log dashboard consists of several key sections that provide detailed information about detected sensitive data.

**Date & Time:** This section displays the date and time when the content or file was added in MangoApps, allowing administrators to track when a policy violation occurred.

**Policy Name:** Each matched entry is associated with a specific policy. This section displays the name of the policy that detected the sensitive information, helping administrators understand which rule was triggered.

**Item Title:** The Item Title section provides the title, subject, or content of the matched item, offering insight into the nature of the flagged content.

**Item Type:** This section identifies the type of content detected, which may include posts, messages, chats, files, pages, wikis, updates, and more.

**Matched Pattern :** Sensitive information is detected based on predefined patterns. This section displays the type of sensitive data found, such as:

* US Social Security Numbers (SSN)
* US Passport Numbers
* US Driver’s License Numbers
* Credit Card Numbers

**Posted By:** Knowing who uploaded or posted the content is crucial for addressing potential policy violations. This section displays the username of the individual responsible for the flagged content.

**Occurrences:** This section shows the number of times sensitive information was found within the content, helping administrators assess the severity of a violation.

**Action Taken:** Based on the policy rules, different actions can be taken when a violation is detected. This section details the response applied to each detected match, such as:

* Logged only
* Logged and notification sent to the admin
* Logged and notification sent to the admin and sender

**Status:** The status section displays whether the detected match is still active or has been resolved, allowing administrators to track ongoing compliance issues.

**Rule Sort:** To refine the displayed matches, users can filter results by selecting a specific policy rule from the available list.

***

### **Download Report (XLS)**

Administrators can download the matches log as an Excel file based on selected filters and policy rules. This feature helps with record-keeping and further analysis.

***

### **Actions via Three-Dot Menu**

Each entry in the Matches Log provides additional actions via the three-dot menu.&#x20;

<figure><img src="/files/vcfInIqqRKRNtSjYypOl" alt="" width="563"><figcaption></figcaption></figure>

These actions help administrators take immediate steps on flagged items.

**View Item:** This action allows administrators to open and review the flagged item directly.

**Message User:** Administrators can send a private message to the user who posted the flagged content. The message dialog automatically fills in the recipient as the sender of the item.

<figure><img src="/files/U2dutGgEeYYPwX1smTCt" alt="" width="563"><figcaption></figcaption></figure>

**Close/Re-Open Alert:** If necessary, administrators can close or re-open the policy alert associated with a matched item, ensuring appropriate handling of compliance issues.

<figure><img src="/files/PscAnb9gd8lqGSzJIl2x" alt=""><figcaption></figcaption></figure>