On macOS endpoints, the Google Drive desktop app does not display the blocked status when a Data in Motion policy rule (Configuration Data Loss PreventionEndpoint DLP Policy) blocks a file transfer from a local drive to Google Drive. Prisma Agent blocks the file transfer but no blocked indicator appears in the Google Drive app.

When configuring a Data at Rest policy rule (Configuration > Data Loss Prevention > Endpoint DLP Policy), the File Types dropdown displays only 58 of 500 supported file types.

Workaround: Select Any to apply the Data at Rest policy rule to all file types supported by Enterprise Data Loss Prevention (E-DLP).

When you configure a Data at Rest policy rule (Configuration Data Loss PreventionEndpoint DLP Policy) with a specific incident Severity, the severity shown in the DLP incident (Configuration Data Loss PreventionDLP Incidents) does not match the configured severity.

(macOS endpoints with Prisma Agent 26.2.0 or 26.2.1 only) When Endpoint DLP is enabled on macOS, print jobs to SMB printers may stop processing after the first two successful prints. The print queue displays an Unable to open the cups file error, and subsequent print jobs remain in a stuck state until the queue is manually cleared.

Workaround: Clear the stuck print jobs from the macOS print queue and restart the printing service.

(macOS endpoints with Prisma Agent 26.2.0 or 26.2.1 only) When Endpoint DLP is enabled on macOS, files saved to DFS or SMB network shares may become corrupted, appearing as 0-byte files or missing entirely. This occurs when the DLP inspection process cannot write the inspected file content back to the original network share path.

Workaround: Save files to a local drive first, then copy them to the network share.

(Windows endpoints with Prisma Agent 26.2.0 or 26.2.1 only) When Endpoint DLP is enabled, files saved to DFS (Distributed File System) network shares on Windows may become corrupted or appear missing. The file content is not written back to the original network path after DLP inspection completes, leaving only an incomplete or empty file on the DFS share.

Workaround: Save files to a local drive first, then copy them to the DFS network share.

Endpoint DLP blocks a Prisma Agent worker thread in the control manager, which prevented proper operation of the agent. This interferes with Prisma Agent worker threads and prevents continuous and correct functionality.

Endpoint DLP generates an additional incident for every file moved from a local device to a USB peripheral device when the file has exFAT file system enabled.

Endpoint DLP generates an additional incident for every write operation from a Microsoft Office application to a network share peripheral device when the write operation contains sensitive data that matches your Endpoint DLP policy rule.

The Excel app open but becomes unresponsive when opening or editing files stored in OneDrive while the Prisma Agent is running with Endpoint DLP policies rules enabled due.

Microsoft Office applications, such as Excel and Microsoft Word, fail to open files from network shares or USB drives on the local device when customers have Endpoint DLP was enabled on the Prisma Agent.

Prisma Agent 25.3.1 randomizes the filename when the end user prints directly from a third party app such as Sublime Text Editor. As a result, Endpoint DLP incidents generated against the printed file display the filename containing randomized numbers and letters.

Prisma Agent 25.3.1 erroneously sends files exceeding the Endpoint DLP Alert and Block Scan Limit Max File Size settings to Enterprise Data Loss Prevention (E-DLP) instead of taking the action configured for the Action When File Size Exceeds Scan Limit setting.