Known Issues in Enterprise DLP Plugin 5.0.5
Focus
Focus
Enterprise DLP

Known Issues in Enterprise DLP Plugin 5.0.5

Table of Contents

Known Issues in Enterprise DLP Plugin 5.0.5

Known issues in Enterprise Data Loss Prevention (E-DLP) plugin 5.0.5.

PLUG-18987

This issue is addressed in Enterprise DLP plugin 5.0.6.
On rare occasions, you are unable to reset theEnterprise DLP plugin from the Panorama™ management server CLI and receive the following error:
DLP reset failure: must be str, not NoneType

PLUG-18713

This issue is addressed in Enterprise DLP plugin 3.0.10 and 5.0.6.
On the Panorama™ management server, Enterprise DLP might fail to delete a data pattern (ObjectsDLPData Filtering Pattern).

PLUG-15192

This issue is addressed in Enterprise DLP plugin 3.0.10.
The Panorama™ management server might fail to synchronize some data profiles created on Strata Cloud Manager and displays the following error:
Cannot update profile on Enforcer. Version passed to Enforcer must be equal to or greater than the onboard version.

PLUG-6145

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).

PAN-144897

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.

DSS-17763

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.