> 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-access/ingest-data-from-prisma-access.md). # Ingest data from Prisma Access Configure Palo Alto Networks data integration for Cortex XDR. You can forward data from Prisma Access to Cortex XDR. When your Cortex XDR tenant begins receiving detection data, it begins stitching logs with other Palo Alto Networks-generated logs to form stories. Use the XQL Search to query the data. Collection of data from multiple accounts is supported. Super User permissions on both the Cortex XDR tenant accounts and the Prisma Access accounts are required for this use case. New tenants (and tenants upgraded from XDR to XSIAM) will work with the new direct integration of Next-Generation Firewall and Panorama into Cortex. For such tenants, there’s no option to use the Strata Logging Service integration. For tenants where customers have integrated directly with Strata Logging Service, the configured integrations, such as Next-Generation Firewall and Prisma Access, can be migrated to Cortex XDR in either of the following ways before the license expires: * More than two weeks before the license for existing integrations with Strata Logging Service expires, manually migrate the integrations, using the corresponding **Migrate Devices** buttons on the **Data Sources & Integrations** page. Make sure you select all your devices to connect directly to Cortex XDR. * Two weeks prior to the end of your Strata Logging Service license, Cortex XDR will automatically migrate your integrations to your Strata Logging Service.

Note

Roll-back of Strata Logging Service integration migration is not supported.

{% hint style="warning" %} ### Prerequisite Configuration of data ingestion from multiple accounts requires Super User permissions in both Cortex XDR tenant and Prisma Access accounts. {% endhint %} {% hint style="info" %} ### Note If you change a device region, you must first disconnect the device from Cortex XDR and then reconnect it after the region change is complete. {% endhint %} The logs ingested by Prisma Access are the same as the logs ingested by Next-Generation Firewall. For more information, refer to [Ingest data from Next-Generation Firewall](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/palo-alto-networks-integrations/next-generation-firewall/ingest-data-from-next-generation-firewall.md). To ingest detection data from Prisma Access: 1. Navigate to **Settings** → **Data Sources & Integrations**. 2. On the **Data Sources & Integrations** page, click **+ Add New**, search for **Prisma Access**, then hover over it and click **Add** or **Add Instance**.

Note

Cortex XDR does not validate your Prisma Access account credentials. You must ensure the account has been deployed in order for data to stream.

3. In the **Connect Prisma Access** dialog box, you can choose to connect Prisma Access to this account or other accounts. * To connect Prisma Access to this account, continue to the next step. * To connect Prisma Access to other accounts, click **Connect Prisma Access from other accounts** and select the account from the accounts listed. 4. **Select log types**: You can either select the specific logs to ingest from this instance, or choose **Select all** to ingest all of them. 5. Click **Connect**.\ Connection can take up to several minutes. On the **Data Sources & Integrations** page, expand Prisma Access to track the status of your instance. 6. Validate that your data is streaming. To ensure the data is streaming into your tenant, using XQL, query Next-Generation Firewall raw datasets `panw_ngfw_<*>_raw` using the field: `is_prisma_mobile`. 7. (Optional) Manage your Instance. After you create the Prisma Access instance, on the **Data Sources & Integrations** page, expand the Prisma Access integration to track the connection, or, if you want, to **Delete** the instance. --- # 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-access/ingest-data-from-prisma-access.md?ask=&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.