> 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/get-started-with-cortex-data-security/use-the-interface.md).

# Use the interface

Cortex Data Security provides a visual map of your data estate to help you understand where sensitive data resides, how it is protected, and which areas require attention.

## Cortex Data Security Command Center

When you log in to Cortex Data Security, the Command Center is the landing page that provides a high-level view of your entire data security posture. After you onboard your cloud, SaaS, DBaaS, and on-premises data sources, the data collected is discovered, classified, and mapped across the visualization.

* **Data sources**: Displayed on the left, this includes ingested sources such as cloud storage, DBaaS databases, on-premises datastores, SaaS applications, and endpoints.
* **Sensitive data assets**: The core of the Command Center highlights assets broken down by sensitivity category (such as PII, Sensitive, and Financial) and identifies AI assets powered by sensitive data.
* **Security modules**: Branching from the core, the Data Security Posture Management (DSPM), Data Loss Prevention (DLP), and Data Detection and Response (DDR) modules summarize open issues, policy violations, and remediation progress.

The Command Center is interactive: selecting a count, branch, or card redirects you to the corresponding inventory or issues view, filtered to the item you selected. For a full breakdown of every section, see [Cortex Data Security Command Center](/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/data-security-dashboards/cortex-data-security-command-center.md).

## Navigate the interface

Use the sidebar menu to access the primary functional areas of Cortex Data Security:

* **Dashboards & Reports**: Access predefined and custom dashboards to monitor specific trends and high-level metrics.
* **Cases & Issues**: View and resolve security findings correlated into unified cases to streamline your response.
* **Investigation & Response**: Perform deep-dive investigations into alerts, logs, and data movement.
* **Threat Management**: Manage the lifecycle of detected threats and coordinate response actions.
* **Posture Management**: Monitor and improve your data security configuration across cloud and on-premises environments.
* **Inventory**: View a consolidated list of your discovered assets, including AI models, applications, APIs, and data assets.
* **Modules**: Access specific functional components for AI Security, Data Security, and Identity Security .
* **Configurations**: Manage foundational settings, such as data source onboarding and integration parameters.

## Next steps

Now that you are familiar with the interface menu, consider the following actions to begin securing your data:

* **Configurations**: [Onboard your cloud accounts and data sources](/data-security-documentation/onboard-and-configure/plan-and-prepare.md).
* **Policies**: Review and customize your [data classification](/data-security-documentation/data-security/data-classification.md) and [security rules and policies](/data-security-documentation/advanced-tools/rules-and-policies.md).
* **Cases & Issues**: [Triage any initial findings](/data-security-documentation/issue-management/cases-and-issues.md) discovered during onboarding.


---

# 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/get-started-with-cortex-data-security/use-the-interface.md?ask=<question>&goal=<endgoal>
```

`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.