> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/l-p-integrations/palo-alto-networks/palo-alto-networks-saas-security-formerly-prisma-saas-setup-for-workbench.md).
# Palo Alto Networks SaaS Security (Formerly Prisma SaaS) Setup for Workbench
*If you need to configure Prisma Cloud Compute, refer to* [*Palo Alto Networks Prisma Cloud Compute Setup for Workbench*](/connect-your-technology/l-p-integrations/palo-alto-networks/palo-alto-networks-prisma-cloud-compute-formerly-twistlock-setup-for-workbench.md)*.*
## Step 1: Generate API Credentials
This procedure creates an authentication that allows Workbench to access the Palo Alto Networks SaaS Security API.
Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech.
1. Log onto the Palo Alto console.
2. In Palo Alto Networks SaaS Security API, select **Settings > External Service**.
3. Click **Add Client App**.
4. Configure the Client App:
* **API Client Name** - enter "Expel".
* **Scopes** - authorize the Expel API client for the following:
* Log access
* Incident management
* Quarantine management
5. Click **Save**.
6. SaaS Security API shows a **Client Secret**. **Copy and save it in a safe place** for use in the next step.
## Step 2: Add Palo Alto Networks SaaS Security as a Security Device in Workbench
Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.
1. [Log in to Workbench](https://workbench.expel.io/).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. In the search box, type “Palo Alto” and then select the **Palo Alto Networks SaaS Security** integration.
4. A configuration pane displays. Complete the fields as follows:
* **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName PAN SaaS Security”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
* **Location** - enter the location of your integration, for example “cloud;” this is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
* **API ID** - enter "Expel".
* **API secret** - enter the secret generated in [Step 1](#uuid-69c88854-6ec7-1326-7d9c-ab7a20ef1b0d_bridgehead-25933).
* **SaaS Security server** - select the server for your region.
5. Click **Save**.
Your device should be created successfully within a few seconds. A few reminders:
* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).
---
# 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://docs.expel.io/connect-your-technology/l-p-integrations/palo-alto-networks/palo-alto-networks-saas-security-formerly-prisma-saas-setup-for-workbench.md?ask=&goal=
```
`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.