1. Expel Support Center
  2. Connect your technology
  3. SaaS integrations

Palo Alto Networks SaaS Security (formerly Prisma SaaS) setup for Workbench

  • Updated

This article explains how to connect Palo Alto Networks SaaS Security to Workbench.

In this article

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. In Palo Alto Networks SaaS Security API, select Settings > External Service.

  2. Click Add Client App.

  3. Type Expel for the API Client Name.

  4. Authorize the Expel API client for these Scopes:

    • Log access

    • Incident management

    • Quarantine management

  5. Click Save.

  6. SaaS Security API shows a Client Secret. Write down the Client Secret and save it.

    Note

    You must have the Client Secret for the next step.

Step 2: Configure the technology in Workbench

Now that we have the correct access configured and noted the credentials, we can integrate your tech with Workbench.

Note

Expel secures all login information our SOC analysts need about your devices in a MFA password product. Access to this login information is protected using our internal MFA processes. To learn more about the IP addresses all Expel traffic comes from, go here.

  1. In a new browser tab, log into https://workbench.expel.io.

  2. On the console page, navigate to Settings and click Security Devices.

  3. At the top right of the page, click Add Security Device.

  4. Search for and select Palo Alto Networks SaaS Security.

  5. For SIEM, select Expel Cloud.

    mceclip2.png

    • Type the Server Name and Location.

    • For API ID, type Expel.

    • For API secret, type the secret generated in Step 1.

    • Select the SaaS Security server from the list.

  6. Click Save.

  7. You can provide console access now or set it up later. Use the instructions below to set it up later.

You can see if the device is healthy on the Security Devices page. It may take a few minutes to see the device listed as healthy.

To check if alerts are coming through, navigate to the Alerts Analysis page. Scroll to the device you want to check and click View alerts. Switch to grid view, then check the list for device alerts. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.

Step 3: Edit the device to add console access

Expel needs console access to your device to allow our SOC analysts to dig deeper during incident investigations. Additionally, our engineering teams use this access to investigate potential health issues, including proper alert ingestion.

Note

Expel secures all login information our SOC analysts need about your devices in a MFA password product. Access to this login information is protected using our internal MFA processes. To learn more about the IP addresses all Expel traffic comes from, go here.

  1. Open Workbench. Go to Organization Settings > Security Devices. Next to the device you just connected, click the down arrow and click Edit.

  2. In the Console Login area, type these details:

    • Console URL: type the console URL from the Server address in the Connection Settings area above. At the end of the URL, type /login.

    • Username: type the user name you created above.

    • Password: type the password you created above.

    • Two-factor secret key (32-character code): depending on how your organization enforces log-ins, this field may not apply to you. In these cases, you can leave it blank. This field is optional and if you have questions or concerns, reach out to your engagement manager or to support.

  3. Click Save.

Tip

This article was accurate at the time of writing, but changes happen. If you find the instructions are outdated, leave a description in the comment field below and let us know!

  • Was this article helpful?

  • 0 out of 0 found this helpful

Related articles