Palo Alto Networks Prisma Cloud Compute (formerly Twistlock) Setup for Workbench
Prerequisites
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.
Log into the Palo Alto console.
Select Settings > Users and then select Add New > Service Account. The Account Details tab appears.
Configure these account details:
Service Account Name - enter "expel_service_account".
Role - select System Admin.
Click Next. The Access Key Details tab appears.
Type an Access Key Name (your choice). Do NOT select Enable Expiration.
Click Save & Create (1 of 2) to generate the key. The Access Key Results screen appears.
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.
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.
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://<LOAD_BALANCER>: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://<IP_ADDRESS>:8083
SaaS Installation
Log into Console.
Go to Manage > System > Utilities.
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.
In the side menu, navigate to Organization Settings > Security Devices.
In the search box, type “Palo Alto” and then select the Palo Alto Networks Prisma Cloud Compute integration.
A configuration pane displays. Complete the fields as follows:

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.
SaaS installation: select Cloud.
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.
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.
Username - enter the Access Key ID created in Step 1.
Password - enter the Secret Access Key created in Step 1.
Server address - enter the console URL determined in Step 2.
Prisma Cloud Compute multi-tenant (only available for on-prem deployments) - select Yes or No.
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.
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.
Last updated
Was this helpful?

