On the Panorama management server, the commit fails if the same profile (

Objects

DLP

Data Filtering Profiles

) is being edited on Panorama and the DLP app at the same time.

Workaround:

If you experience a commit failure when editing the data filtering profile on Panorama, you must discard the edits, reset the Enterprise DLP plugin, and reconfigure the data filtering profile.

On the Panorama management server, a Panorama administrator (

Panorama

Administrators

) with a custom admin role (

Panorama

Admin Roles

) allowing read and write access to Enterprise DLP data patterns (

Objects

DLP

Data Filtering Patterns

) and profiles (

Objects

DLP

Data Filtering Profiles

) are able to only read Enterprise DLP data patterns and profiles.

Additionally, a Panorama administrator with full read and write access to the Panorama web interface can only read Enterprise DLP data patterns and profiles.

On the Panorama management server, predefined data filtering profiles (

Objects

DLP

Data Filtering Profiles

) are not displayed because the Panorama

admin

administrator (

Panorama

Administrators

) does not exist.

Workaround:

Create the

admin

user.

Firewalls leveraging Enterprise Data Loss Prevention (DLP) that do not have connectivity to the Internet through a management network are not able to push Enterprise DLP Settings (

Device

Setup

DLP

) to the DLP cloud service.

Firewalls leveraging Enterprise Data Loss Prevention (DLP) do not display the Enterprise DLP data filtering profiles (

Objects

DLP

Data Filtering Profiles

) or Enterprise DLP Settings (

Device

Setup

DLP

), and cannot be overridden locally on the firewall.

Uploading the same file multiple times with different file names to the Enterprise Data Loss Prevention (DLP) cloud service causes the DLP details in the data filtering log (

Monitor

Logs

Data Filtering

) of the subsequent file uploads to display the original file name of the file.

For example, if a file name with the name File_A is uploaded to the DLP cloud service and the same file is then uploaded with the name File_B, the data filtering Log Details displays the file name File_B but the DLP log details displays the name File_A. Additionally, any newly uploaded files with the same content but different file name display the new file name in the data filtering Log Details but display the original file name in the DLP log details.

On the Panorama management server, you cannot create an admin role (

Panorama

Admin Roles

) to control access to Enterprise Data Loss Prevention (DLP) filtering settings and snippet configuration (

Device

Setup

DLP

).

On the Panorama management server, you are unable to view the Enterprise Data Loss Prevention (DLP) log details (

Monitor

Logs

Data Filtering

DLP

) if the Enterprise DLP and Cloud Services plugins are both installed.

Workaround:

Uninstall the Cloud Services plugin (

Panorama

Plugins

).

Firewalls leveraging Enterprise Data Loss Prevention (DLP) do not display the on-device Help for the DLP Settings (

Device

Setup

DLP

).

Enterprise Data Loss Prevention (DLP) data filtering profiles (

Objects

DLP

Data Filtering Profiles

) names do not display in Data Filtering logs (

Monitor

Logs

Data Filtering

) until a commit is performed on firewalls leveraging Enterprise DLP after you successfully install the Enterprise DLP plugin.

Enterprise Data Loss Prevention (DLP) data profile

Thread ID/Name

filter is not available when you configure a custom report (

Manage

Manage Custom Reports

) on the Panorama management server or locally on a firewall leveraging Enterprise DLP.