> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/data-security-dashboards/data-security-dashboard.md).
# Data Security dashboard
The Data Security dashboard helps you discover and visualize all your data assets across your different cloud services, so you can understand where your sensitive data is, how it is used, and how it is moving across the organization. It provides a focused view of your data estate, its sensitive content, and its exposure, helping you prioritize where to apply protection and remediation.
The following image shows the Data Security dashboard:
## How to access the Data Security dashboard
The Data Security dashboard is a system-provided predefined dashboard.
To open it, select **Dashboards & Reports → Dashboard**, then choose **Data Security** from the dashboard drop-down menu in the header.
The dashboard is read-only and cannot be edited or deleted. To build your own version, select **Save as new** to create a custom dashboard you can modify while preserving the original. For more information, see [Data Security dashboards](/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/data-security-dashboards.md).
The dashboard is interactive. Selecting a widget value, issue, or asset redirects you to the corresponding inventory or issues view, filtered to the item you selected.
## Assets discovered
The header summarizes the total number of data assets discovered across your environment, along with the number of data store services covered.
Next to the total, a row of provider cards shows the number of assets discovered per data source—such as AWS, Azure, GCP, Snowflake, Microsoft Office 365, Databricks, On-Premise, and Google Workspace—giving you a single view of where your data lives.
Select a provider card to drill into the assets discovered for that source.
## Asset type breakdown
Below the header, a row of cards breaks the discovered assets down by type, each with a total count:
* **AI Data Assets:** Data assets associated with your AI pipelines.
* **Backups:** Backup assets discovered across your environment.
* **Databases:** Databases discovered across your data sources.
* **Disks:** Disk assets, such as EBS volumes and cloud disks.
* **SaaS Assets:** Assets discovered in your onboarded SaaS applications.
* **Storage Buckets:** Object storage buckets discovered across your cloud providers.
Select an asset type card to open the corresponding assets in the inventory.
## Top Data Security Issues to Address
Displays the highest priority data security issues to remediate to improve your data security posture. Each issue shows a description, the date it was first discovered, and the number of times it was detected.
Select an issue to open the corresponding issue details, or select **Show All Issues** to open the full issues inventory.
## Data location map and data patterns
An interactive world map plots where your data assets are located geographically, with markers sized to reflect concentration, helping you understand data residency and where sensitive data is stored.
Alongside the map, the **Data Patterns** panel lists the data patterns detected across your assets—such as Email Address, IBAN, Phone Number, Last Name, IP Address, Country, Street Address, and Social Security Number—each with the number of matches found.
You can hide data patterns from the map using the panel.
## Exposure Issues
Displays the number of exposed sensitive objects, broken down by exposure type:
* **Open to world:** Objects that are publicly accessible.
* **Public objects in private storage:** Public objects located inside otherwise private storage.
* **Shared with foreign project:** Objects shared outside their expected project boundary.
Select an exposure type or **View All** to open the corresponding exposed objects for remediation.
## Data Footprint Findings
Displays the number of exposed sensitive objects associated with data hygiene findings, broken down by type:
* **Empty Storage Assets:** Storage assets that contain no data.
* **Storage Asset with Shadow Backups:** Storage assets with unmanaged or unexpected backups.
Select a finding type or **View All** to review the assets and reduce your data footprint.
## Sensitive Asset Types
Displays the total number of sensitive objects in your environment, along with the **Top 5 Sensitive Asset Types** ranked by object count.
Select an asset type to drill into the sensitive objects of that type, or select **View All Services** to see the full breakdown across all services.
## Top Assets at Risk
Displays the assets with the highest risk, each with its name, asset type, and management status.
Select an asset to open its details and the issues detected on it, or select **View All** to open the full list of assets at risk.
For a broader overview of the platform and the full data inventory reference, see [What is Cortex Data Security?](/data-security-documentation/get-started-with-cortex-data-security/readme.md) and [Data inventory](/data-security-documentation/inventory-and-monitoring/asset-management/data-inventory.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/data-security-dashboards/data-security-dashboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.