> 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-xpanse/integrations/ingest-cloud-resources-from-prisma-cloud/configure-the-prisma-cloud-integration-in-cortex-xpanse.md).

# Configure the Prisma Cloud Integration in Cortex Xpanse

Enable Cortex Xpanse to ingest Prisma Cloud data.

Before you begin this task, you must generate an API access key and secret key in Prisma Cloud. See [Generate an API Access Key in Prisma Cloud](/cortex-xpanse/integrations/ingest-cloud-resources-from-prisma-cloud/generate-an-api-access-key-in-prisma-cloud.md).

1. Navigate to **Settings** → **Configurations** → **Data Collection** → **Collection Integrations.**
2. Click **+ Add Instance** for **Prisma Cloud**.
3. In the **Collection Integration** window, complete the information as follows:

   1. Enter a descriptive **Name** of your choice.
   2. In the **Access Key ID** field, enter your Prisma Cloud API access key ID.
   3. In the **Secret Key** field, enter your Prisma Cloud secret key.
   4. In the **Service URL** field, enter the URL for your Prisma Cloud instance.

      The Prisma Cloud URL is different between the UI and APIs. Customers that log into <https://app3.prismacloud.io> should input <https://api3.prismacloud.io> as the Service URL.
   5. In the **Business Unit** field, select the business unit you’d like to assign these assets to in Xpanse.

   ![prisma-cloud-integration-configuration.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-1adbbc398f2f0d5c6aca43e998991a466e4a53a7%2F1b2155b3893eacacab883354049d4539fe16bebb7e69599fc6d29ff50601a2d8.png?alt=media)
4. Click **Add Integration**.

   Prisma Cloud data may take up to 48 hours to be ingested into your Cortex Xpanse Expander instance.

Once you've configured the Prisma Cloud collection integration it may take up to 48 hours for new asset records, services, websites, alerts, and incidents to appear. This is because the collection process must run multiple times to ensure that data is only loaded for high confidence resources and can be properly combined with Xpanse global scan findings.

If after 48 hours you don't see new assets, services, websites, alerts, or incidents, check for errors on the collection integration configuration page in **Settings**. You should also confirm that you've properly configured access to all of the desired account groups in Prisma Cloud.


---

# 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-xpanse/integrations/ingest-cloud-resources-from-prisma-cloud/configure-the-prisma-cloud-integration-in-cortex-xpanse.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.