Set Up Prerequisites for Custom Target Adapters
Focus
Focus
Prisma AIRS

Set Up Prerequisites for Custom Target Adapters

Table of Contents

Set Up Prerequisites for Custom Target Adapters

Before creating and using custom target adapters, deploy the Network Channel client, enable the adapter sidecar, and create a Network Channel.
Where Can I Use This?What Do I Need?
  • Prisma AIRS (AI Red Teaming)
Your adapter runs inside the adapter sidecar, a container bundled with the Network Channel client Helm chart. To create or activate an adapter, deploy the Network Channel Helm chart at v1.4.0 or later, enable the adapter sidecar, and create a Network Channel for the target's network.
  1. Create a Network Channel for the target's network in AI Red Teaming.
    You will select this channel when you create or activate an adapter and again when you attach the adapter to a target. A channel is required to activate an adapter; it is optional when saving a draft.
    An active Network Channel is required to host and execute adapter code.
  2. Install the panw-network-client Helm chart at version v1.4.0 or later on your cluster.
    v1.4.0 is the minimum release that bundles the adapter runner. Verify that the client shows connected status in AI Red Teaming before proceeding.
    The Network Channel server enforces a minimum client version for adapter traffic. If your chart is older than v1.4.0, upgrade it before enabling the adapter sidecar.
  3. Enable the adapter sidecar using one of the following methods.
    1. In the chart's values.yaml, set adapterSidecar.enabled to true:
      adapterSidecar: enabled: true
    2. Alternatively, pass the flag directly on the helm upgrade command:
      helm upgrade --install <release> <chart> --set adapterSidecar.enabled=true
      Enabling the sidecar adds the adapter-sidecar container listening on localhost:8010 to the Network Channel pod and switches the client into adapter-aware mode.
  4. Verify your cluster's network policy and pod security settings.
    Network policy and pod hardening are your responsibility. The chart ships recommended security defaults (readOnlyRootFilesystem, runAsNonRoot, dropped capabilities). Keep these defaults unless your cluster policy requires otherwise.