> 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-prisma-cloud-compute-formerly-twistlock-setup-for-workbench.md).
# Palo Alto Networks Prisma Cloud Compute (formerly Twistlock) Setup for Workbench
## Prerequisites
1. You must have the System Administrator role on Prisma Cloud Compute to add a service account.
## Step 1: Add Service Account
Service accounts differ from user accounts in that they don't need an email address associated with them and don't need to be validated or activated in an external system before they can be used.
{% hint style="info" %}
Think carefully about the information you provide, because after you create a service account, you can't make changes. You must delete it and start over.
{% endhint %}
1. Log into the Palo Alto console.
2. Select **Settings > Users** and then select **Add New > Service Account**. The Account Details tab appears.
3. Configure these account details:
* **Service Account Name** - enter "expel\_service\_account".
* **Role** - select **System Admin**.
4. Click **Next**. The Access Key Details tab appears.
5. Type an **Access Key Name** (your choice). *Do **NOT** select **Enable Expiration**.*
6. Click **Save & Create (1 of 2)** to generate the key. The Access Key Results screen appears.
7. Click **Download .csv file** to download your access key as a .csv file and then store it in a secure location. *Access keys are not stored on Prisma Cloud Compute, so **this is the only opportunity you have to download it**.*
8. To view the new service account, select **Settings > Users** and enter the service account name in the **Search** field. If there is a problem with the service account, delete it and start over at [step 1](#h_01hye6z19j92hc110whmdgy4py).
## Step 2: Determine Prisma Cloud Compute Console URL
Prisma Cloud Compute can be either a self-hosted or SaaS installation. The Prisma Cloud Compute console URL depends on your specific installation. Use the following sections to determine your Prisma Cloud Compute console URL.
### Self-hosted Installation
For self-hosted environments, the Prisma Cloud Compute API is exposed on port 8083 (HTTPS). This port is specified at install time in twistlock.cfg.
* For Kubernetes Installations (most common):
* Console service is exposed by a LoadBalancer.
* The console URL is the LoadBalancer followed by port 8083: `https://:8083`
* For Onebox installations:
* Console installed on a standalone host.
* The Console URL is the IP address or DNS name of the host followed by port 8083: `https://:8083`
### SaaS Installation
1. Log into Console.
2. Go to **Manage > System > Utilities**.
3. The console URL is listed under **Path to Console** at the bottom of the page.
## Step 3: Add PAN Prisma Cloud Compute 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 Prisma Cloud Compute** integration.
4. A configuration pane displays. Complete the fields as follows:
5. In the Where is your device? section, select one of the following depending on your installation:
* **Self-hosted installation:** select **On-prem** and then select **Assembler** from the list. Select the assembler you set up in [Add a New Assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md).
* **SaaS installation**: select **Cloud**.
6. **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName PAN Prisma Cloud Compute”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
7. **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.
8. **Username** - enter the **Access Key ID** created in [Step 1](#h_01hye6z19j92hc110whmdgy4py).
9. **Password** - enter the **Secret Access Key** created in [Step 1](#h_01hye6z19j92hc110whmdgy4py).
10. **Server address** - enter the **console URL** determined in [Step 2](#h_01hye6z19jhj92ymfhap83ca09).
11. **Prisma Cloud Compute multi-tenant** (only available for on-prem deployments) - select **Yes** or **No**.
12. Select **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-prisma-cloud-compute-formerly-twistlock-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.