# How to View Outbound File Transfer Records on Client Endpoints

Canonical: https://www.nsecsoft.com/en/course/leaktrack-list.html

Language: en-US

Updated: 2026-11-04T08:05:07.776924Z

When an enterprise has enabled Leakage Tracking, administrators can view the endpoint's outbound file records in the console\. Such records are an important basis for determining whether employees have sent files in violation of regulations, uploaded information abnormally, or transferred business documents through unauthorized channels\. They are also one of the core entrances for subsequent \[…\]

When an enterprise has enabled

**Leakage Tracking**

, administrators can view the endpoint's outbound file records in the console. Such records are an important basis for determining whether employees have sent files in violation of regulations, uploaded information abnormally, or transferred business documents through unauthorized channels. They are also one of the core entrances for subsequent evidence collection and review.

Compared with simply seeing "an employee has made outgoing actions", the value of outgoing records lies in being able to drill down further to view file information, outgoing channels and behavioral details. Therefore, it is recommended that administrators not only pay attention to the existence of records during daily inspections, but also focus on suspicious paths, suspicious file types, and high-frequency abnormal behaviors.

#### **View steps**

1\. Enter the

**Data Security**

module in the Ping32 Management Console.

2\. Click

**Leak Tracking**

, and the outbound file records of the client computer will be displayed at the bottom of the page.

3\. Double-click any outgoing record to view more detailed information, including:

-   Leak basic information
-   Sensitive content of the document
-   File information
-   Leakage route information
-   Leaked document transfer process

![](<https://www.nsecsoft.com/site-assets/bd479a7e2f6829c160217f5ef8075eb7317c364c4447adfeb14f5da8239c94ec/f0f9b5910be8607a8312f35a5e58ea9b348c24578e9da9bcbe7fdfcda13256b4/4a2d7bad1c5a0b9596b35733df97594a2f559cf6d7dfcc6f23891c6f285b3357/3-leaktrack-list-1.png>)

#### **Usage suggestions**

-   It is recommended to pay priority to whether there are any obvious abnormalities in the outbound channel, file name, risk level and time of occurrence.
-   For suspicious records, it is recommended to enter the details page to further check the file attributes, sensitive content hits and transfer process, and avoid making judgments based on a single field in the list.
-   If the enterprise also enables outbound file backup or Smart Screenshots, outbound records can be viewed in conjunction with backup files and screen records to improve review efficiency.

#### **Reference for troubleshooting ideas**

In actual audits, administrators can first make judgments from three directions: first, whether the outgoing behavior occurs during abnormal time periods, such as after get off work, holidays, or batch concentrated outgoing periods; second, whether the outgoing route is abnormal, such as through personal chat tools, browser uploads, or outgoing through unusual programs; third, whether the file itself is abnormal, such as the file type does not match job responsibilities, hits sensitive content, or has a high risk level. By viewing the records in this way, it is usually easier to find the events that really need to be dealt with than by simply browsing them one by one.