> 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/cortex-xdr-5.x/protect-your-endpoints/endpoint-dlp/dlp-status-in-all-endpoints.md).

# DLP status in all endpoints

View DLP and browser extension status for managed Cortex XDR endpoints.

The **All Endpoints** page provides a central location from which you can view and manage the endpoints on which the agent is installed. In addition to the extensive information that Cortex offers on all its endpoints, you can now view **DLP Status** and **DLP Extension Status**. This enables you to track information about the DLP browser extension and its status.

By default, this option is hidden. If you are using DLP, you need to add the fields DLP Status and DLP Extension Status when analyzing the status of endpoints with DLP.

<details>

<summary>DLP status</summary>

**DLP Status** provides the following statuses:

{% hint style="info" %}

### Note

It is recommended to work with the latest security content.
{% endhint %}

* **Active (Compatible)**
* **Update required**: Indicates that the system's engine version does not match the version defined in the policy, and an update is necessary.
* **Failed to start**: Indicates that there was an initialization error. This could occur because of the DLP policy, or the DLP engine on the machine is not working.
* **Degraded**: Indicates that there are specific issues, such as custom detector patterns that require pattern fixes, that is causing DLP not to function.

</details>

<details>

<summary>DLP extension status</summary>

The agent monitors the endpoints for information when the extension is installed and performs periodic refreshes to ensure accurate results.

The DLP extension status shows the installation status of the extension on the endpoint:

* **Installed (x)**: The x represents the number of extensions installed.
* **Not installed**: This indicates that the extension was either uninstalled or was never installed.
* **No value**: Where DLP is not activated on the endpoint.
* **Installed but unactivated**: This indicates that either a supported browser is not being used or the DLP extension has not been activated yet.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Close and reopen your browser to activate the DLP extension.</p></div>

You can drill down from the endpoint to view details of the DLP Extension Status.

From the selected endpoint, right-click and select **Endpoint Data** → **View DLP Extension Status**. This opens a dialog box that shows the extension status for both Chrome and Edge extensions.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/endpoint-dlp/dlp-status-in-all-endpoints.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
