|
| 1 | +--- |
| 2 | +pcx_content_type: reference |
| 3 | +title: Data security analytics |
| 4 | +--- |
| 5 | + |
| 6 | +The Data security analytics dashboard reports security issues and sensitive data found within your SaaS applications, cloud environments, and HTTP traffic. It visualizes event data collected from your DLP and CASB policies. If neither DLP nor CASB is enabled in your account, the dashboard appears empty. |
| 7 | + |
| 8 | +To view the Data security analytics dashboard: |
| 9 | + |
| 10 | +1. Log into [Zero Trust](https://one.dash.cloudflare.com). |
| 11 | +2. Go to **Analytics** > **Dashboards**. |
| 12 | +3. Select **Data security analytics**. |
| 13 | + |
| 14 | +## Prerequisites |
| 15 | + |
| 16 | +To populate this dashboard, you must have: |
| 17 | + |
| 18 | +- [Data Loss Prevention (DLP)](/cloudflare-one/policies/data-loss-prevention/) configured to generate event data from scanned web traffic or SaaS applications. |
| 19 | +- At least one [Cloud Access Security Broker (CASB)](/cloudflare-one/applications/casb/) integration connected to capture findings from your SaaS applications or cloud environments. |
| 20 | + |
| 21 | +## Available insights |
| 22 | + |
| 23 | +The dashboard includes the following panels and metrics: |
| 24 | + |
| 25 | +- [SaaS and Cloud findings by count](/cloudflare-one/insights/analytics/data-analytics/#saas-and-cloud-findings-by-count) |
| 26 | +- [Posture findings by Severity](/cloudflare-one/insights/analytics/data-analytics/#posture-findings-by-severity) |
| 27 | +- [DLP matches in HTTP requests over time](/cloudflare-one/insights/analytics/data-analytics/#dlp-matches-in-http-requests-over-time) |
| 28 | +- Top integrations by posture findings |
| 29 | +- Top integrations by content findings |
| 30 | +- Top cloud resources by findings |
| 31 | +- Top users by DLP policies triggered |
| 32 | + |
| 33 | +### SaaS and Cloud findings by count |
| 34 | + |
| 35 | +The SaaS and Cloud findings by count chart shows a time series view of Posture and Content findings. [Posture](/cloudflare-one/applications/casb/manage-findings/#posture-findings) denotes posture findings which include misconfigurations, unauthorized user activity, and other data security issues. [Content](/cloudflare-one/applications/casb/manage-findings/#content-findings) denotes content findings which include instances of potential data exposure as identified by [DLP](/cloudflare-one/policies/data-loss-prevention/). |
| 36 | + |
| 37 | +Each bar represents the total number of findings detected within a given time interval. You can use this view to observe patterns or spikes in findings over time. Hover over any bar to view the exact count of Posture and Content findings for that period. |
| 38 | + |
| 39 | +To review findings in detail, log into [Zero Trust](https://one.dash.cloudflare.com) and go to **CASB** > **Posture Findings** or **Content Findings**. |
| 40 | + |
| 41 | +### Posture findings by Severity |
| 42 | + |
| 43 | +The Posture findings by severity chart displays the distribution of CASB findings based on their [severity levels](/cloudflare-one/applications/casb/manage-findings/#severity-levels). Each segment of the circle represents the number of posture issues classified as `Critical`, `High`, `Medium`, or `Low`. |
| 44 | + |
| 45 | +To review findings in detail, log into [Zero Trust](https://one.dash.cloudflare.com) and go to **CASB** > **Posture Findings**. |
| 46 | + |
| 47 | +### DLP matches in HTTP requests over time |
| 48 | + |
| 49 | +The DLP matches in HTTP requests over time chart displays when [DLP policies](/cloudflare-one/policies/data-loss-prevention/dlp-policies/) were triggered by users over a specified period of time. |
| 50 | + |
| 51 | +Unlike the SaaS and Cloud findings by count chart above, which relies on CASB findings from data at rest, the DLP matches in HTTP requests over time chart reflects DLP detections in HTTP traffic — helping you monitor sensitive data movement in real time. |
| 52 | + |
| 53 | +To review DLP detections in detail, log into [Zero Trust](https://one.dash.cloudflare.com) and go to **Logs** > **Gateway** > **HTTP**. Use the **DLP profiles** or **DLP match data** filters to view HTTP requests that triggered a DLP policy. |
0 commit comments