Prisma Access
Palo Alto Networks - Strata Cloud Manager Pack.#
This Integration is part of the#
Prisma Access IntegrationIntegrate with Prisma Access to monitor the status of the Service, alert and take actions. The integration uses both the Panorama XML API and SSH into the PAN-OS CLI.
#
Common parametersThe Server Host or IP parameter is required by both.
#
SSH connectionThe following commands require the SSH access to be configured:
- prisma-access-active-users
- prisma-access-cli-command
- prisma-access-query
The SSH connection requires the SSH Credentials for CLI, Password and SSH Port are provided.
SSH credentials should be your username and password for the PAN-OS CLI - they can be tested using a standalone SSH client to verify that you are able to connect to the CLI on the SSH port.
#
API connectionThe following commands require the API access to be configured:
- prisma-access-logout-user
The API connection requires the API Port and API Key parameters as well as a Device Group or Vsys.
This integration was integrated and tested with version 9.0.7 of Prisma Access
#
Configure Prisma Access on Cortex XSOAR- Navigate to Settings > Integrations > Servers & Services.
- Search for Prisma Access.
- Click Add instance to create and configure a new integration instance.
Parameter | Description | Required |
---|---|---|
server | Server Host or IP (e.g., 10.1.1.9 or panorama.my.domain) | True |
port | API Port (e.g 443) | False |
key | API Key | False |
insecure | Trust any certificate (not secure) | False |
proxy | Use system proxy settings | False |
device_group | Device group - Panorama instances only (write shared for Shared location) | False |
vsys | Vsys - Firewall instances only | False |
sshport | SSH Port | False |
Username | SSH Credentials for CLI | False |
- Click Test to validate the URLs, token, and connection.
#
CommandsYou can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.
#
prisma-access-logout-userForce logout a specific user from Prisma Access
#
Base Commandprisma-access-logout-user
#
InputArgument Name | Description | Required |
---|---|---|
user | Username to logout. (Without domain name - e.g. jsmith) | Required |
domain | Domain name of the user to logout. | Required |
computer | Computer name to logout. | Required |
tenant_name | The tenant name. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
PrismaAccess.LogoutUser | unknown | LogoutUser command results |
#
Command Example!prisma-access-logout-user user="jsmith" domain="acme" computer="jsmithPC"
#
prisma-access-queryRun a query via the Prisma Access CLI
#
Base Commandprisma-access-query
#
InputArgument Name | Description | Required |
---|---|---|
query | Query to run. Example input: querystring limit=2000 action getGPaaSLast90DaysUniqueUsers | Required |
#
Context OutputPath | Type | Description |
---|---|---|
PrismaAccess.QueryResults | unknown | Query results |
#
Command Example!prisma-access-query query="querystring limit=2 action getGPaaSActiveUsers"
#
prisma-access-cli-command (deprecated)Run a custom CLI command on Prisma Access
#
Base Commandprisma-access-cli-command
#
InputArgument Name | Description | Required |
---|---|---|
cmd | CLI command to run (e.g. debug plugins cloud_services gpcs query querystring limit=9000 action getGPaaSLast90DaysUniqueUsers) | Required |
#
Context OutputThere is no context output for this command.
#
Command Example!prisma-access-cli-command cmd="show system info | match hostname"
#
prisma-access-active-users (deprecated)Query currently active users.
#
Base Commandprisma-access-active-users
#
InputArgument Name | Description | Required |
---|---|---|
limit | Maximum number of entries to return. Default is 20. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
PrismaAccess.ActiveUsers | unknown | Active Users on Prisma Access |
#
Command Example!prisma-access-active-users limit=10