> 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/configure-cortex-xdr/cortex-xdr-data-sources/palo-alto-networks-integrations/prisma-browser-integration.md).

# Prisma Browser Integration

Configure Palo Alto Networks data integration for Cortex XDR.

When Prisma Browser (PB) is installed on an endpoint, Cortex XDR correlates browser-layer telemetry from PB with OS-layer process events on managed endpoints. This integration provides unified visibility and forensic analysis across both web and system activity within the Cortex XDR console, and is displayed in the Issues card.

#### Data Flow

* Telemetry Ingestion: Prisma Browser streams endpoint browser telemetry directly into Cortex Data Lake (CDL).
* Causality Stitching: Cortex XDR correlates browser events with the Cortex XDR agent’s OS-level process causality chains, mapping user browser interactions directly to underlying system process executions.
* Incident Generation: Security-critical browser events—such as browser tampering, unauthorized modifications, or web-delivered malware—automatically trigger Cortex XDR alerts and incidents.
* Unified Forensics: Analysts can investigate the complete execution chain from initial browser interactions down to kernel-level process activities in a single timeline.


---

# 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/configure-cortex-xdr/cortex-xdr-data-sources/palo-alto-networks-integrations/prisma-browser-integration.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.