Health and Telemtry Use Cases
Focus
Focus
Enterprise DLP

Health and Telemtry Use Cases

Table of Contents

Health and Telemtry Use Cases

Critical use cases for leveraging Enterprise Data Loss Prevention (E-DLP) Health & Telemetry dashboard to troubleshoot and diagnose issues and ensure data security compliance.
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)
  • SaaS Security Inline
  • Data Security
  • Prisma AIRS
  • 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
  • Prisma Pro
The following use cases demonstrate how to leverage the Enterprise Data Loss Prevention (E-DLP) Health & Telemetry dashboard for critical operational scenarios. These use cases address real pain points and provide guidance for achieving rapid issue resolution, performance optimization, and compliance validation.

Diagnosis of Transaction Failures

Scenario: Users report that file uploads to a commonly used app have suddenly started to get unexpectedly blocked. You need to determine if it was a legitimate Enterprise DLP match, configuration issue, or network issue unrelated to Enterprise DLP.
  1. Log in to Strata Cloud Manager.
  2. Review the Reasons for Inspection Failure for user traffic associated with the recent unexpected activity.
    Use these logs to begin understanding the nature of your transaction failures. In some cases, it may require reaching it to Palo Alto Networks Customer Support to resolve.
    For example, inspection failures can be caused by the enforcement point itself due to over utilization of resources or a missing Enterprise DLP data profile. Alternatively, a network issue could be causing file uploads times to exceed the settings.
  3. Select ConfigurationData Loss PreventionHealth & Telemetry.
  4. Apply the following filters:
    • Apply the File Content Type filer.
    • Use the Application filter to narrow down the Health & Dashboard data for the specific app the user reported the unexpected block.
    • Apply the Past 24 Hours time filter.
  5. Review the transaction Throughput graph to understand whether Enterprise DLP successfully Completed inspection of uploaded files or if there is a large spike of Errors or Timeouts.
    If you see a large volume of Completed transactions it likely means there was a change in your data patterns that is now preventing uploads. Review your audit logs to understand the changes made to your data protection policy and communicate them to your organization.
  6. Review the Top 5 Failure Reasons transaction widget to understand what might be causing the unexpected file blocks.
    • File is password protected or encrypted—Enterprise DLP can't inspect password-protected or encrypted files. If you see a high volume of this failure reason, review whether your enforcement points are forwarding encrypted files that should be excluded from inspection.
    • Unable to Read File—Enterprise DLP failed to inspect the forwarded file because the file is damaged, the file type is unsupported, or content extraction failed. This can include failures to extract text data from images using Optical Character Recognition (OCR) due to low image quality or over-utilization of resources in Enterprise DLP.
    • Internal Scan Error—An internal Enterprise DLP error prevented inspection. If you see a high volume of internal scan errors, check the Enterprise DLP service status to confirm all services are operational.

Data-Driven Performance Optimization

Scenario: Your organization is experiencing frequent scan timeouts on large files. This is forcing trade-offs between security and workflow efficiency.
  1. Log in to Strata Cloud Manager.
  2. Select ConfigurationData Loss PreventionHealth & Telemetry.
  3. Apply the following filters to analyze your large file processing patterns:
    • Apply the File Content Type filter.
    • Use the File Type filter to select large document types your users commonly upload.
    • Apply the Past 30 Days time filter to capture sufficient performance data for analysis.
  4. Analyze the Transaction Summary widgets to understand the scope of your timeout issues.
    Review the Timeouts count compared to Completed and Request Volume to calculate your current timeout rate. A timeout rate above 5% may indicate performance tuning opportunities.
    Compare Data Volume to Request Volume to understand the average file sizes being processed, as larger files are more likely to experience timeouts.
  5. Review the transaction Throughput graph to identify timeout patterns over time.
    Look for periods when Timeouts spike compared to Completed transactions. These patterns can help you identify:
    • Peak usage periods when system load contributes to timeouts
    • Consistent timeout rates that suggest configuration issues
    • Sudden increases that might indicate new file types or data patterns causing processing delays
    Click the Download button to export the throughput data in CSV or SVG format for detailed statistical analysis of your processing times.
  6. Analyze the Top 5 Data Profiles widget to identify configuration bottlenecks.
    Data profiles that frequently appear in this widget may contain patterns that are particularly resource-intensive for your specific file types. Consider whether these profiles are essential for all file types or if they can be optimized or applied more selectively.
  7. Use the Top 5 Applications or File Types widget to focus your optimization efforts.
    Toggle between viewing by Applications and File Types. File types with high Completed counts but low incident rates may be good candidates for timeout optimization, as they represent high-volume, low-risk processing.
  8. Apply additional filters to isolate performance bottlenecks:
    • Use the Region filter to determine if performance issues are localized to specific geographic areas, which could indicate network latency contributions.
    • Apply the Channel filter to compare performance across your enforcement points.
  9. Based on your analysis, adjust your data filtering settings.
    • Increase the File Movement Max Latency to allow more time for the enforcement point to forward the file. This helps reduce the number of timeouts you experience.
    • Optimize data profile selection by removing resource-intensive patterns from high-volume, low-risk file types identified in your analysis.
    • If network latency is a factor, consider adjusting the Action When Max Latency is Reached from Block to Alert for non-critical workflows.
  10. Monitor the impact of your changes.
    Use a Custom time period to compare before and after performance metrics. Track the reduction in timeout rates in the Transaction Summary while ensuring that security coverage is maintained by monitoring the Incidents count in the Top 5 Applications or File Types widget.
    After implementing changes, continue monitoring the Top 5 Failure Reasons widget to ensure that timeout reductions don't result in other types of processing issues.

Configuration Troubleshooting

Scenario: A data pattern that was working suddenly stops detecting sensitive data, requiring rapid independent diagnosis.
  1. Log in to Strata Cloud Manager.
  2. Review the audit logs for recent configuration changes that might affect pattern detection.
    Check for recent changes to data patterns, profiles, or policies that might explain the sudden reduction in detections. Look specifically for:
    • Data profile modifications or updates
    • Pattern regex changes or new pattern deployments
    • Policy rule modifications that might affect pattern evaluation precedence
  3. Select ConfigurationData Loss PreventionHealth & Telemetry.
  4. Apply the following filters to establish a baseline comparison:
    • Apply the Past 7 Days time filter and review the Transaction Summary widgets to understand current Completed, Errors, and Timeouts volumes.
    • Use the Application filter to focus on the specific apps where sensitive data should be detected.
    • Apply the File Type filter if the issue appears to be related to specific data formats.
  5. Compare recent detection rates to historical performance by changing the time filter to Past 30 Days.
    A significant drop in the 7-day versus 30-day incident rate suggests a recent configuration issue. If you see a large volume of Completed transactions but proportionally fewer Incidents in the Top 5 Applications or File Types widget, this indicates that data is being processed but patterns are not matching as expected.
  6. Review the Top 5 Applications or File Types widget to identify where pattern detection has declined.
    Toggle between Applications and File Types view to see which have high Completed counts but unexpectedly low Incidents. These are your primary candidates for configuration troubleshooting.
    • High completed, low incidents—Likely indicates pattern configuration issues rather than processing failures.
    • Consistent incident patterns—May indicate the issue is isolated to specific data types or applications.
    • Complete absence of incidents—Could suggest policy precedence issues or pattern deployment problems.
  7. Use the transaction Throughput graph to pinpoint when the pattern detection issue began.
    Look for a steady volume of Completed transactions without a corresponding increase in Errors or Timeouts. This pattern typically indicates a configuration change rather than a system performance issue. Note the specific timeframe and correlate it with any configuration changes from your audit log review.
  8. Analyze the Top 5 Data Profiles widget to identify profiles experiencing unusual error rates or processing issues.
    Data profiles that suddenly appear in the errors/timeouts list may indicate recent configuration problems:
    • New profiles in error list—May indicate pattern syntax errors or resource-intensive patterns causing timeouts.
    • Missing expected profiles—Could suggest deployment issues or profile version mismatches.
    • Increased error rates—Might indicate compatibility issues with new data formats.
  9. Check the Top 5 Failure Reasons widget for clues about data processing or format changes.
    • File is password protected or encrypted—A sudden increase may indicate changes in how files are being shared or new encryption policies applied to documents that were previously unencrypted.
    • Unable to Read File—May indicate changes in file formats, encoding, or new file types that Enterprise DLP cannot properly process for pattern analysis.
    • Internal Scan Error—Could suggest internal Enterprise DLP processing issues that correlate with the detection decline.
    If you see low error rates alongside reduced incidents, this most likely indicates pattern configuration issues rather than system processing problems.
  10. Apply additional filters to narrow the scope of your configuration troubleshooting:
    • Use the Channel filter to determine if the issue affects all enforcement points or is isolated to specific channels like NGFW, Endpoint DLP, or Prisma Access.
    • Apply the Region filter to check if the problem is location-specific, which could indicate deployment synchronization issues.
    • Use the Content Type filter to isolate whether the issue affects File, Non-File data, or both.
  11. Based on your analysis, validate and correct the identified configuration issues:
    • Review your data profiles for recent modifications that correlate with the detection decline timeline.
    • Test pattern matching against sample data that should trigger detection to verify pattern functionality.
    • Check for policy rule precedence issues where competing rules might prevent pattern evaluation.
    • Verify that data profile updates have been properly deployed across all relevant enforcement points identified in your channel analysis.
  12. Monitor your corrections using a Custom time period to validate that pattern detection effectiveness has been restored.
    After implementing fixes, track the recovery in Incidents count in the Top 5 Applications or File Types widget and confirm that the applications and file types you identified now show improved detection rates. Continue monitoring the Top 5 Data Profiles widget to ensure your corrections don't introduce new processing issues.

Compliance and Forensic Investigation

Scenario: Auditors require proof that all sensitive data transfers were properly inspected, with forensic capability for any failures.
  1. Log in to Strata Cloud Manager.
  2. Review any existing DLP incidents and audit logs for the investigation period to understand the scope of data handling.
    Begin by understanding what incidents were generated and what configuration changes occurred during the audit period. This provides context for your comprehensive analysis and helps identify any gaps that need explanation.
    Document any incidents that required investigation or remediation actions, as auditors will want to understand how these were handled and resolved.
  3. Select ConfigurationData Loss PreventionHealth & Telemetry.
  4. Define the audit scope using precise time and context filters:
    • Use the Custom time range to match the exact audit period required by your compliance framework or regulatory request.
    • Apply Region filters if the audit covers specific geographic areas or data residency requirements.
    • Use Application filters if auditing specific business applications or data flows critical to compliance.
    • Apply Channel filters to include all relevant enforcement points in scope.
  5. Generate comprehensive coverage metrics from the Transaction Summary widgets to demonstrate Enterprise DLP monitoring effectiveness.
    Document the following metrics to prove comprehensive data protection coverage during the audit period:
    • Total Data Volume processed—Demonstrates the scope of data under Enterprise DLP protection
    • Total Request Volume—Shows the number of individual data transfer instances inspected
    • Percentage of Completed inspections versus total requests—Proves inspection coverage rates
    • Total Incidents generated in the Top 5 Applications or File Types widget—Demonstrates active detection of policy violations and sensitive data exposure attempts
  6. Account for all exceptions and provide business justifications using the Transaction Summary data.
    Auditors will scrutinize any data that was not successfully inspected. Use the summary widgets to provide complete accountability:
    • Document all Errors with explanations from the Top 5 Failure Reasons widget
    • Explain all Timeouts and show that timeout settings were appropriately configured for business requirements
  7. Analyze the Transaction Throughput graph to demonstrate consistent monitoring throughout the audit period.
    Use the throughput data to show that Enterprise DLP was actively and consistently processing traffic during the entire audit timeframe. Highlight any periods of reduced throughput and provide explanations:
    • Consistent processing patterns—Shows reliable DLP operation during business hours
    • Maintained incident detection—Demonstrates ongoing security effectiveness
    • Explained anomalies—Any unusual patterns correlated with business events, maintenance windows, or system updates
    Use the Download function to export the throughput data in CSV or SVG format for inclusion in formal audit documentation.
  8. Document policy effectiveness and configuration management using the Top 5 widgets.
    • Use the Top 5 Applications or File Types widget to show that high-risk data sources were actively monitored and that incidents were generated when appropriate
    • Reference the Top 5 Data Profiles widget to demonstrate that any profiles with high error rates were identified and remediated during the audit period
    • Use the Top 5 Failure Reasons to show proactive monitoring and management of system issues that could affect security effectiveness
  9. Generate audit trail documentation with appropriate access controls and data protection measures.
    • Export all relevant dashboard data using the download capabilities, ensuring RBAC controls are properly applied and documented
    • Capture screenshots of key widgets showing coverage metrics, incident patterns, and failure analysis with timestamps
    • Document the correlation between Health & Telemetry data and specific DLP incidents that required investigation or action
    • Include references to configuration changes during the audit period from audit logs and show how these supported security objectives
  10. Validate data retention and privacy compliance requirements.
    Confirm that all transaction data is available for the full audit period and document your data governance practices:
    • Verify that data is available for up to 90 days as configured, meeting regulatory retention requirements
    • Document encryption-at-rest and access control measures that protect audit data during retention
    • Reference your data export and longer-term archival procedures if retention beyond 90 days is required
    • Demonstrate compliance with applicable privacy regulations such as GDPR or CCPA through proper data handling and deletion audit trails
  11. Prepare executive summary and recommendations based on your comprehensive analysis.
    Summarize your findings to demonstrate Enterprise DLP effectiveness and any areas for improvement:
    • Overall coverage percentage and security effectiveness during the audit period
    • Key incidents detected and resolved, showing active protection of sensitive data
    • Any system improvements implemented during the audit period to enhance security or performance
    • Recommendations for future configuration optimizations based on usage patterns and performance data