Activate Transporter

The Transporter over Broker VM enables secure communication between Cortex Cloud and self-hosted integrations, such as Version Control Systems (VCS) and SonarQube Server.

Whether you need a Transporter depends on your domain's accessibility:

• Private domains: A Transporter is required. Because Cortex Cloud cannot directly reach on-premises hosts, a direct connection to a private domain will fail. The Transporter bridges this connection securely without exposing your internal network
• Public domains: A Transporter is not needed. Configure an egress rule instead

Prerequisites

• Permissions: To configure and manage Transporter applet settings, you must have permissions to manage Broker Service configurations (such as an Instance Administrator)
• Set up and configure Broker VM: Set up and configure Broker VM
• Confirm that your Broker is v 28 or above
• Whitelist IP addresses to enable access to Cortex XSIAM resources. The IP addresses for the Transporter are in the Broker VM Resources section of the Enable access to required PANW resources document
• Open port 4052, which is required for the Transporter's IP address communication
• Open Port 443 (outbound), which is required for the Broker VM to pull data from your version control system (VCS)

License

To gain access to and use the Transporter applet, you must possess one of these license types: Cloud Posture Security or Runtime Management) or XSIAM Premium. If you plan to use the Transporter for Code Security scanning, you will also need the Code Security add-on license.

The Transporter applet is not supported for FedRAMP customers.

How to activate the Transporter applet

1. Select Settings → Configurations → Broker VMs (under Data Broker.
2. Select the Brokers tab → locate your Broker VM → hover and click + Add under the Apps column → AppSec Transporter.
3. Configure the Transporter connection in the provided fields:

• Transporter Name (required). Requires a unique name as you can integrate multiple applets for different integrations
• Provider Self Signed CA Certificate Path: Specify the file path for a custom Certificate Authority (CA) certificate used by the Transporter to securely communicate with services

1. Click Save.
2. Verify connectivity: Navigate to the Apps column and verify that your AppSec Transporter applet has been added and displays a connected status.
3. Next step: After activating the Transporter, proceed to configure the Transporter applet on your self-managed VCS data source instance. For more information, refer to Set up a Transporter on your VCS.

Manage Transporter applets

To manage Transporter applet configurations, disable connections, or deactivate an applet, navigate to the Broker VMs page. From there, select your Appsec Transporter under the App column.

• Edit applet configurations: Select the Appsec Transporter under the App column → Configure. You are redirected to the Transporter applet settings to manage its configurations
• Disable applet connection for a single integration:

  1. Select the Appsec Transporter under the App column → Configure.
  2. On the Transporter applet configurations page, click on the specific Transporter applet → Disable. This disables the specific integration, but it can be re-enabled.
• Deactivate an applet (all connections): Select the Appsec Transporter under the App column → Deactivate → Confirm when prompted All existing connections are deleted but their configurations are saved in the database. When adding a new connection, you'll be prompted if you want to reuse previous configurations.