> For the complete documentation index, see [llms.txt](https://help.radiantsecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.radiantsecurity.ai/radiant-connectors/cloud-and-infrastructure/palo-alto-networks-prisma-cloud.md).

# Palo Alto Networks Prisma Cloud

Palo Alto Networks Prisma Cloud is a cloud-native application protection platform that secures cloud accounts, workloads, and services against misconfigurations, threats, and compliance gaps. Connecting Prisma Cloud forwards its security alerts to Radiant Security through the Prisma Cloud API. Radiant uses the alert data to triage these alerts in context, giving analysts faster verdicts on whether a flagged cloud resource or activity is a real risk or expected behavior.

At the end of this configuration, you provide Radiant Security with the following values:

* **API URL**
* **Access Key ID**
* **Secret Access Key**
* **Prisma ID** (optional)

### Prerequisites

* [ ] System Admin access to Prisma Cloud

### Generate API credentials in Prisma Cloud

1. On the Prisma Cloud Console, select **Settings** > **Access Control** > **Access Keys**, then select **Add** > **Access Key**.
2. Enter a **Name** for the key (e.g., `Radiant Security Integration`).
3. Select **Enable Expiration** and set an expiry term that meets your compliance standards. Without expiration, the key never expires. Radiant recommends a one-year term.
4. Click **Save**.

{% hint style="info" %}
Copy and store the Access Key ID and Secret Access Key now. They cannot be retrieved later.
{% endhint %}

### Get your API URL and Prisma ID

**API URL**

Your console URL changes by region. Find your region and copy the matching API URL from [Prisma Cloud's API URLs reference](https://pan.dev/prisma-cloud/api/cspm/api-urls/).

{% hint style="warning" %}
Copy the Prisma Cloud API URL, not the Prisma Cloud admin console URL.
{% endhint %}

**Prisma ID** (optional)

Provide the Prisma ID only in a multi-tenant environment.

1. From the console, select **Settings** > **License Information** or **Account Settings**.
2. On the **License** page, find the **Prisma ID** value and copy it.

### Add the data connector in Radiant Security

1. Log in to [Radiant Security](https://app.radiantsecurity.ai/).
2. From the navigation menu, select **Settings** > **Data Connectors**, then click **+ Add Connector**
3. Select **Palo Alto Prisma Cloud** from the list, then click **Credentials**.
4. Under **Credential Name**, enter an identifiable name (e.g., `Prisma Cloud API`).
5. Under **Required Credentials**, enter the values you collected:
   * **API URL**
   * **Access Key ID**
   * **Secret Access Key**
   * **Prisma ID** (optional)
6. Click **Add Connector** to save the configuration.

### Verify ingestion

After Palo Alto Networks Prisma Cloud begins forwarding, confirm alerts and events are reaching Radiant.

1. In Radiant, navigate to [Log Management](https://app.radiantsecurity.ai/logs).
2. Filter by `rs_connectorType:"pan_prisma"`.
3. Confirm recent alerts and events appear.

{% hint style="info" %}
Allow several minutes for alerts and events to be parsed, indexed, and available for search.
{% endhint %}


---

# 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://help.radiantsecurity.ai/radiant-connectors/cloud-and-infrastructure/palo-alto-networks-prisma-cloud.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.