On the Panorama management server, the web interface becomes unresponsive when editing large data profiles (ObjectsDLPData Filtering Profiles).

On the Panorama management server, the Enterprise DLP plugin fails to complete post commit tasks and causes all commits (CommitCommit to Panorama) to get stuck at 99%.

The Panorama management server is unable to a generate report if a data filtering log (MonitorLogsData Filtering) with Report ID of 0 for a DLP incident. A DLP Incident has a Report ID of 0 if the DLP cloud service was unable to scan the file.

The Panorama management server is unable to synchronize new data profiles (ObjectsDLPData Filtering Profiles) from the DLP cloud service.

On the Panorama management server, the list of predefined URL categories are not displayed for a data profile configured for non-file inspection (ObjectsDLPData Filtering Profiles<select a data profile>URL Category List Excluded From).

On the Panorama management server, Enterprise Data Loss Prevention (E-DLP) allows you to create multiple data filtering profiles (ObjectsDLPData Filtering Profiles) with the same Name.

On the Panorama management server, data filtering profiles (ObjectsDLPData Filtering Profiles) with the .gzip file type specified do not display after you install the latest Apps & Threats dynamic update version (PanoramaDevice DeploymentsDynamic Updates). This results in commit failures if the data filtering profile is associated with a Security policy rule (PoliciesSecurity).

Workaround: If installing the latest Apps & Threats dynamic update is required, remove the impacted data filtering profiles from Security policy rules or modify the specified file types.

On the Panorama management server, an outdated default DLP block response page is displayed when traffic matches a data filtering profile with the Action set to Block when leveraging Enterprise DLP.

Creating a new data profile from the Panorama management server CLI fails.

Workaround: Create a new data profile from the Panorama web interface.

Firewalls leveraging Enterprise Data Loss Prevention (DLP) do not display the Enterprise DLP data filtering profiles (ObjectsDLPData Filtering Profiles) or Enterprise DLP Settings (DeviceSetupDLP), and cannot be overridden locally on the firewall.

On the Panorama management server, you cannot create an admin role (PanoramaAdmin Roles) to control access to Enterprise Data Loss Prevention (DLP) filtering settings and snippet configuration (DeviceSetupDLP).

On the Panorama management server, data pattern (ObjectsDLPData Filtering Patterns) match criteria and data filtering profiles (ObjectsDLPData Filtering Profiles) that contain the word fail or failure cause all data patterns and data filtering profiles to not display.

Workaround: Remove any instance of the words fail or failure from all your data patterns and data filtering profiles.

Enterprise Data Loss Prevention (DLP) data profile Thread ID/Name filter is not available when you configure a custom report (ManageManage Custom Reports) on the Panorama management server or locally on a firewall leveraging Enterprise DLP.

On the Panorama management server, custom data profiles (ObjectsDLPData Filtering Profiles) are not synchronized to the DLP cloud service if you have an active CASB-X license. This prevents you being able to associate the data profile with a Security policy rule and displays the error Data Profile does not exist.

Workaround: Contact Palo Alto Networks Support to restore synchronization functionality between the DLP cloud service and Panorama.