Enterprise DLP
DLP App
Table of Contents
DLP App
View the log details for traffic that matches your
Enterprise Data Loss Prevention (E-DLP)
data profiles
on the DLP app on the hub.- Log in to the DLP app on the hub.If you don’t already have access to the DLP app on the hub, see the hub Getting Started Guide. Only Superusers can access the hub.
- View the DLPIncidents.
- Select aScan DateandRegionto filter the DLP Incidents.Enterprise DLPIncidents are generated in theRegionwhere the Public Cloud Server is located.ForPanoramaandPrisma Access (Managed by Panorama), the region is determined by the currently configured Public Cloud Server. By default, theEnterprise DLPplugin is configured to resolve to the closest Public Cloud Server to where the inspected traffic originated but you can configure a static Public Cloud Server.ForStrata Cloud Manager,Enterprise DLPautomatically resolves to the closest Public Cloud Server to where the inspected traffic originated.When a new Public Cloud Server is introduced,Enterprise DLPbegins to automatically resolve to it if it’s closer to where the inspected traffic originated. ForPanoramaandPrisma Access (Managed by Panorama), this happens only if you keep the default Public Cloud Server FQDN. ForStrata Cloud Manager, this happens by default.This might mean that new DLP Incidents generated after the release of a new Public Cloud Server are generated in a differentRegion.
- Review the DLP Incidents summary information to help focus your incident investigation.These lists are updated hourly.
- Top Data Profiles to Investigate—Lists data profiles with the highest number of incidents in descending order.
- Top Sources to Investigate—Lists up to seven source IP addresses and Fully Qualified Domain Names (FQDN) with the highest number of incidents in descending order.
- Sensitive Files by Action—Lists the number of incidents based on the Action taken in descending order.
- Review the Incidents and click aFilename to review a specific incident.You can filter the DLP incidents byFile NameorReport IDto search for a specific incident you want to review.
- Review the Incident Details to review specific file upload details.Make note of theReport IDfor the DLP incident if you haven’t already done so. The Report ID is used to view additional Traffic log details regarding the DLP incident.
- Review theMatches within Data Profilesto review snippets of matching traffic and the data patterns that matched the traffic to better understand what data was detected.For nested data profiles, the data profile displayed is the specific nested data profile that matched the scanned traffic. For example, you create aDataProfile, with the nested profilesProfile1,Profile2, andProfile3and scanned traffic matches the nestedProfile2and is blocked. In this scenario, the data profile displayed for the incident isProfile2.
- In the snippet,Enterprise DLPonly masks traffic that matches the data pattern match criteria. Other sensitive data captured in the snippet are not masked if they do not match the data pattern where the snippet is displayed.
- Data pattern match criteria configured to inspect forAnyoccurrence of matched traffic display up to 3Highand 3Lowconfidence level matches if detected.
- Data pattern match criteria configured to inspect forHighconfidence level matches display up to 3Lowconfidence level matches if detected.
- Data pattern match criteria configured to inspect forLowconfidence level matches display up to 3Highconfidence level matches if detected.