Enterprise DLP Health and Telemetry
Focus
Focus
Enterprise DLP

Enterprise DLP Health and Telemetry

Table of Contents

Enterprise DLP Health and Telemetry

Monitor and diagnose Enterprise Data Loss Prevention (E-DLP) performance and data transaction flows for enhanced tuning and troubleshooting.
Where Can I Use This?What Do I Need?
  • NGFW (Managed by Panorama or Strata Cloud Manager)
  • Prisma Access (Managed by Panorama or Strata Cloud Manager)
  • Prisma Browser
  • Enterprise Data Loss Prevention (E-DLP) license
    Review the Supported Platforms for details on the required license for each enforcement point.
Or any of the following licenses that include the Enterprise DLP license
  • Prisma Access CASB license
  • Next-Generation CASB for Prisma Access and NGFW (CASB-X) license
  • Data Security license
The Enterprise Data Loss Prevention (E-DLP) Health & Telemetry dashboard is a unified, self-service interface for monitoring and diagnosing Enterprise DLP system performance and transaction flows across all your enforcement points. This interface provides insights into your Enterprise DLP deployment for tuning and troubleshooting.
Traditional DLP system tuning and troubleshooting often lack visibility into scan performance and face difficulties diagnosing failures. The Health & Telemetry dashboard addresses these challenges in your environment, reducing guesswork and lengthy support engagements.
Enterprise DLP integrates transaction data directly into the Health & Telemetry dashboard, DLP Incident Manager, and Strata Logging Service. The Strata Logging Service ingests, processes, and aggregates your Enterprise DLP transaction data across all enforcement points in your network. This aggregated data feeds to the Health & Telemetry dashboard for high-level metrics and to the DLP Incident Manager for detailed drill-down analysis.
Review the Health &Telemetry Dashboard Use Cases to learn about different ways to use the Health & Telemetry dashboard to achieve rapid issue resolution, performance optimization, and compliance validation.
  • Filters
    Filter all widgets in the Health & Telemetry dashboard using any combination of available filters.
    • Application—Select one or more apps. Enterprise DLP displays only the apps associated with forwarded traffic, and not all supported apps.
    • File Type—Select one or more file types. Enterprise DLP displays only the file types associated with forwarded traffic, and not all supported file types.
    • Channel—Select the enforcement channels. You can select NGFW, Endpoint DLP, Prisma Access, and Prisma Browser.
    • Region—Select one or more supported regions where forwarded traffic originated.
    • Content Type—Select the forwarded traffic content type. You can select File or Non-File.
    • Time Filter—Define the time frame for data displayed in the Health & Telemetry dashboard. You can select Past 15 Minutes, Past 60 Minutes, Past 3 Hours, Past 24 Hours, Past 7 Days, Past 30 Days, Past 60 Days, or Past 90 Days. Alternatively, you can define a Custom time frame.
  • Transaction Summary Widgets
    The Transaction Summary widgets provide a high-level overview of traffic forwarded to Enterprise DLP.
    • Data Volume— Cumulative size of all file and non-file content forwarded to Enterprise DLP. This includes the full payload of files as well as the byte-count of non-file traffic, such as web form data or chat messages.
    • Request Volume—Total number of unique instances of file and non-file traffic forwarded to Enterprise DLP.
    • Completed—Total number of unique instances of forwarded traffic that Enterprise DLP successfully inspected that either contained no sensitive data or generated a DLP incident because Enterprise DLP detected sensitive data.
    • Errors—Total number of unique instances of forwarded traffic that Enterprise DLP failed to inspect due to a data, configuration, or service errors that prevented inspection.
    • Timeouts—Total number of unique instances of forwarded traffic that Enterprise DLP failed to complete because the session length to forward traffic exceeded the Max Latency settings configured in the data filtering settings.
  • Transaction Throughput
    The Transaction Throughput is a line graph displaying the number of requests per second that were forwarded to Enterprise DLP over a specified time period. The requests signify the total number of unique instances of traffic forwarded to Enterprise DLP for inspection and verdict rendering.
    You can click the request status to remove it from the Transaction Throughout graph. Click the Download button to download the graph data in CSV or SVG format.
    The Transaction Throughput graphs depicts the total number of:
    • Completed requests.
      This is all requests that Enterprise DLP that contained no sensitive data or that Enterprise DLP blocked or generated an alert for because sensitive data was detected.
    • Requests that couldn't be completed due to Errors.
      In some cases, Enterprise DLP encounters data, configuration, or service errors that prevent inspection of forwarded traffic.
    • Requests that exceeded the Data Filtering Timeouts settings.
      You can configure the Max Latency settings to specify the maximum time allowed for the enforcement point to forward.
  • Top 5 Transaction Widgets
    Enterprise DLP includes three Top 5 Transaction widgets allowing you to quickly see the most salient Enterprise DLP health and telemetry activity. The data displayed in the Top 5 Transactions widgets is based on the currently applied filters.
    • Top 5 Applications or File Types—View the top 5 Applications by App-ID or File Types. For the top apps or file types, you can view the list based on the total number of Completed inspections of forwarded traffic or the total number of Incidents generated.
    • Top 5 Data Profiles—View the top 5 data profiles that had sensitive traffic matches but experienced data, configuration, or service Errors or instances of session Timeouts that the prevented Enterprise DLP from successfully inspecting forwarded traffic and rendering a verdict.
    • Top 5 Failure Reasons—The top 5 reasons for Enterprise DLP inspection failures. Enterprise DLP lists the total count of each unique occurrence where Enterprise DLP failed to inspect forwarded traffic. This widget can display:
      • File is password protected or encrypted—Can't inspect password-protected files or encrypted files.
      • Unable to Read File—Enterprise DLP failed to inspect the forwarded file due to one of the following reasons:
        • File damaged and can't be inspected.
        • Unsupported file type forwarded. Enterprise DLP can only inspect supported File Types.
        • File content extraction failed.
      • Internal Scan Error—File content extraction and inspection failed due an internal error.