Skip to main content

EULA & Infrastructure

Manage the Red Team end-user license agreement, compute instances, devices, container registry credentials, and network broker channels.

Prerequisites​

  • Prisma AIRS CLI installed and configured (Installation)
  • AIRS management credentials set (mgmtClientId, mgmtClientSecret, mgmtTsgId in the selected tenant file)

EULA​

The Red Team EULA must be accepted before launching scans. Three subcommands manage the lifecycle.

Check Acceptance Status​

airs-cli redteam eula status

Returns whether the EULA has been accepted, when, and by whom.

View EULA Content​

airs-cli redteam eula content

Displays the full EULA text.

Accept the EULA​

airs-cli redteam eula accept

Fetches the current EULA content and submits acceptance. This is a one-time operation per tenant.


Instances​

Red Team instances represent dedicated compute environments for running adversarial scans. Full CRUD is available via airs-cli redteam instances.

Create an Instance​

airs-cli redteam instances create \
--tsg-id <tsgId> \
--tenant-id <tenantId> \
--app-id <appId> \
--region <region>
FlagRequiredDescription
--tsg-id <id>YesTenant Service Group ID
--tenant-id <id>YesTenant ID
--app-id <id>YesApplication ID
--region <region>YesDeployment region

Get Instance Details​

airs-cli redteam instances get <tenantId>

Returns the instance configuration: TSG ID, tenant ID, app ID, and region.

Update an Instance​

airs-cli redteam instances update <tenantId> \
--tsg-id <tsgId> \
--tenant-id <tenantId> \
--app-id <appId> \
--region <region>

Delete an Instance​

airs-cli redteam instances delete <tenantId>

Devices​

Devices are attached to Red Team instances and represent the scanning infrastructure.

Create Devices​

airs-cli redteam devices create <tenantId> --config devices.json

The config file contains the device specification as JSON.

Update Devices​

airs-cli redteam devices update <tenantId> --config devices.json

Performs a PATCH update on the device configuration.

Delete Devices​

airs-cli redteam devices delete <tenantId> --serial-numbers <serials>
FlagRequiredDescription
--serial-numbers <serials>YesComma-separated serial numbers to delete

Registry Credentials​

Fetch time-limited container registry credentials for pulling Red Team infrastructure images:

airs-cli redteam registry-credentials

Returns a token and its expiry timestamp.


Network Broker​

The network broker relays traffic between Red Team clients and targets that aren't directly reachable from the AIRS data plane — for example, a model served inside a private Kubernetes cluster or homelab. Each relay is a channel; a broker client running next to the target connects to its channel and forwards scan traffic.

Channels live on a distinct data-plane endpoint from the rest of the Red Team API. Override it with PANW_RED_TEAM_NETWORK_BROKER_ENDPOINT (or redTeamNetworkBrokerEndpoint in ~/.prisma-airs/config.json); OAuth credentials are shared with the other Red Team commands (the tenant's mgmt* keys).

Channel Statistics​

See the broker server domain, container image/registry, helm chart, client version, and online/total channel counts:

airs-cli redteam network-broker stats

List Channels​

airs-cli redteam network-broker channels list
# Filter by status; structured output
airs-cli redteam network-broker channels list --status ONLINE DRAFT --output json

Each channel reports a status — ONLINE, OFFLINE, or DRAFT — plus its connected-client count and last-online timestamp.

Create & Inspect a Channel​

airs-cli redteam network-broker channels create --name "prod-relay" --description "Production broker"
airs-cli redteam network-broker channels get <channelId>

A newly created channel starts in DRAFT with all features disabled; it becomes usable once a broker client connects to it.

Update a Channel​

airs-cli redteam network-broker channels update <channelId> --name "renamed" --description "…"
note

The API authorizes channel updates server-side. A DRAFT channel created via the API but not yet claimed by a connected broker client may return 403 Access denied on update — this is a platform authorization decision, not a CLI error. There is no channel-delete endpoint; remove unwanted channels from the Strata/SCM console.