# Collect Palo Alto Prisma SD-WAN logs

**Parser Version:** 3.0
Supported in:

This document explains how to ingest Palo Alto Prisma SD-WAN (formerly CloudGenix) logs to Google Security Operations using the Bindplane agent.

Palo Alto Prisma SD-WAN is a cloud-delivered software-defined wide area network solution that provides application-aware routing, centralized policy management, and automated branch connectivity. It simplifies WAN operations by replacing traditional router-centric networks with a secure, application-defined fabric that optimizes performance and reduces costs.

For more information, see [Palo Alto Prisma SD-WAN documentation](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/cloudgenix-sdwan).

## Before you begin

Make sure you have the following prerequisites:

- A Google SecOps instance
- A Windows 2016 or later or Linux host with `systemd`
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
- Privileged access to the Palo Alto Prisma SD-WAN management console (Strata Cloud Manager or legacy CloudGenix Controller)
- Network connectivity between the Bindplane agent host and the Prisma SD-WAN ION devices

## Get Google SecOps credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

- **New deployments**: Use the Chronicle API (Option 1).
- **Legacy deployments**: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.

### Option 1: Create a service account for the Chronicle API (recommended)

1. Sign in to the [Google Cloud console](https://console.cloud.google.com/) and select the Google Cloud project that is linked to your Google SecOps instance.
2. Go to **IAM \& Admin \> Service Accounts**.
3. Click **Create service account**.
4. Provide the following configuration details:
   - **Service account name** : Enter a name for the account (for example, `bindplane-ingest`).
   - **Service account description** : Enter a description (for example, `Bindplane agent log ingestion`).
5. Click **Create and continue**.
6. In the **Grant this service account access to project** section, click **Select a role** and select **Chronicle Editor**.
7. Click **Continue** , and then click **Done**.
8. Click the service account you created, and then go to the **Keys** tab.
9. Click **Add key \> Create new key**.
10. Select **JSON** and click **Create**. The key file is downloaded to your computer.
11. Save the key file as `ingestion-auth.json` in the Bindplane collector directory (`/opt/observiq-otel-collector/ingestion-auth.json` on Linux or `C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json` on Windows), or update `creds_file_path` in `config.yaml` to match the path where you save it.
12. Go to **IAM \& Admin \> Settings** and copy the **Project number**. You'll need it for the exporter configuration.

> [!NOTE]
> **Note:** The JSON key is a credential. Restrict access to the file on the Bindplane host and rotate the key according to your organization's policy.

### Option 2: Download the ingestion authentication file (legacy)

1. Sign in to the Google SecOps console.
2. Go to **Settings \> Data Management \> Collection Agents** . If you are on a SIEM-only platform, go to **Settings \> Collection Agents**.
3. Download the **ingestion authentication file**.
4. Save the file securely on the system where the Bindplane agent will be installed.

> [!NOTE]
> **Note:** This file authenticates the agent to the legacy Ingestion API (`malachiteingestion-pa.googleapis.com`), which Google has scheduled for end of life on July 20, 2027. Plan to move to Option 1 before that date.

## Get Google SecOps customer ID

1. Sign in to the Google SecOps console.
2. Go to **Settings \> Administration \> Profile** . If you are on a SIEM-only platform, go to **Settings \> Profile**.
3. Copy and save the **Customer ID** from the **Organization Details** section.

## Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

### Windows installation

1. Open **Command Prompt** or **PowerShell** as an administrator.
2. Run the following command:

       msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet

3. Wait for the installation to complete.

4. Verify the installation by running:

       sc query observiq-otel-collector

   The service should show as **RUNNING**.

### Linux installation

1. Open a terminal with root or sudo privileges.
2. Run the following command:

       sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh

3. Wait for the installation to complete.

4. Verify the installation by running:

       sudo systemctl status observiq-otel-collector

   The service should show as **active (running)**.

### Additional installation resources

For additional installation options and troubleshooting, see [Bindplane agent installation guide](https://docs.cloud.google.com/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).

> [!NOTE]
> **Note:** The Chronicle API exporter configuration requires Bindplane collector v1.106.0 or later. The previous commands install the latest release. If you're updating an existing installation, upgrade the collector before changing the configuration.

## Configure the Bindplane agent to ingest syslog and send to Google SecOps

### Locate the configuration file

- **Linux:**

      sudo nano /opt/observiq-otel-collector/config.yaml

- **Windows:**

      notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"

### Edit the configuration file

- Replace the entire contents of `config.yaml` with the following configuration:

      receivers:
        udplog:
          listen_address: "0.0.0.0:514"

      exporters:
        chronicle/cloudgenix_sdwan:
          protocol: https
          # Region of your instance, for example us, europe, asia-southeast1
          location: <LOCATION>
          # Project number of the Google Cloud project linked to the instance
          project: '<PROJECT_NUMBER>'
          compression: gzip
          creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
          customer_id: '<CUSTOMER_ID>'
          endpoint: chronicle.googleapis.com
          log_type: CLOUDGENIX_SDWAN
          raw_log_field: body
          ingestion_labels:
            env: production

      service:
        pipelines:
          logs/cloudgenix_to_chronicle:
            receivers:
              - udplog
            exporters:
              - chronicle/cloudgenix_sdwan

### Configuration parameters

Replace the following placeholders:

- **Receiver configuration:**

  - `listen_address`: IP address and port to listen on. Use `0.0.0.0` to listen on all interfaces. Port `514` is standard for syslog (requires root privileges on Linux; use `1514` for non-root).
- **Exporter configuration:**

  - `creds_file_path`: Full path to the service account JSON key file (Option 1).
    - **Linux** : `/opt/observiq-otel-collector/ingestion-auth.json`
    - **Windows** : `C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json`
  - `<CUSTOMER_ID>`: Google SecOps customer ID.
  - `location`: Replace `<LOCATION>` with the region of your Google SecOps instance (for example, `us`, `europe`, or `asia-southeast1`). The exporter prefixes `chronicle.googleapis.com` with this value. See [Regional Endpoints](https://docs.cloud.google.com/chronicle/docs/reference/rest?rep_location=us#regional-service-endpoint) for the complete list.
  - `project`: Replace `<PROJECT_NUMBER>` with the project number from **IAM \& Admin \> Settings**.
  - `endpoint`: Keep set to `chronicle.googleapis.com`.

### Legacy ingestion API exporter

- If you use the ingestion authentication file from Option 2, replace the `exporters` block with the following. Set `creds_file_path` to the path to the ingestion authentication file, and if your instance is outside the US, replace `malachiteingestion-pa.googleapis.com` with your [regional endpoint](https://docs.cloud.google.com/chronicle/docs/reference/ingestion-api#regional-endpoints) (for example, `europe-malachiteingestion-pa.googleapis.com`).

      exporters:
        chronicle/cloudgenix_sdwan:
          compression: gzip
          creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
          customer_id: '<CUSTOMER_ID>'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: CLOUDGENIX_SDWAN
          raw_log_field: body
          ingestion_labels:
            env: production

> [!NOTE]
> **Note:** This exporter will stop working when the Ingestion API is discontinued on July 20, 2027.

### Save the configuration file

- After editing, save the file:

  - **Linux** : Press `Ctrl+O`, then `Enter`, then `Ctrl+X`
  - **Windows** : Click **File \> Save**

## Restart the Bindplane agent to apply the changes

- To restart the Bindplane agent in **Linux**, run the following command:

      sudo systemctl restart observiq-otel-collector

  1. Verify the service is running:

         sudo systemctl status observiq-otel-collector

  2. Check logs for errors:

         sudo journalctl -u observiq-otel-collector -f

- To restart the Bindplane agent in **Windows**, choose one of the following options:

  1. Command Prompt or PowerShell as administrator:

         net stop observiq-otel-collector && net start observiq-otel-collector

  2. Press `Win+R`, type `services.msc`, and press Enter.

  3. Locate **observIQ OpenTelemetry Collector**.

  4. Right-click and select **Restart**.

  5. Verify the service is running:

         sc query observiq-otel-collector

  6. Check logs for errors:

         type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"

## Configure Palo Alto Prisma SD-WAN syslog forwarding

You can configure syslog forwarding on individual ION devices or create a reusable syslog profile that can be applied across multiple devices.

### Option 1: Configure syslog export on an individual ION device

1. Sign in to the **Strata Cloud Manager** with administrator privileges.
2. Go to **Configuration \> Prisma SD-WAN \> ION Devices \> Claimed**.
3. Select the ION device that you want to configure for syslog forwarding.
4. Click **Configure the device**.
5. Select **Syslog Export**.
6. Click **Create Syslog Server**.
7. Select **Enable this Syslog Server**.
8. Provide the following configuration details:
   - **Name** : Enter a descriptive name (for example, `SecOps-Bindplane`).
   - **Server IP** or **Server FQDN** : Select **Server IP** and enter the IP address of the Bindplane agent host (for example, `192.168.1.100`).
   - **Server Port** : Enter `514` (or the port configured in the Bindplane agent). Default ports are `514` for TCP or UDP and `6514` for TLS.
   - **Protocol** : Select **UDP** (default), **TCP** , or **TLS**.
   - **Severity Level** : Select **critical** , **major** , or **minor**. Logs and events for the selected severity level and higher are exported.
9. To export flow logs, enable the **Flow Logging** option.
10. Click **Save**.
11. Verify that syslog messages are being received by checking the Bindplane agent logs.

    > [!NOTE]
    > **Note:** The maximum number of syslog servers supported per ION device is 16. ION devices use the syslog RFC 5424 format for all protocols.

### Option 2: Create a reusable syslog profile

1. Sign in to the **Strata Cloud Manager** with administrator privileges.
2. Go to **Configuration \> Prisma SD-WAN \> Profiles and Templates \> Syslog**.
3. Click **Create Syslog Profile**.
4. Provide the following configuration details:
   - **Name** : Enter a name for the syslog profile (for example, `SecOps-Bindplane`).
   - **Description**: Optionally, enter a description.
   - **Server IP** or **Server FQDN** : Select **Server IP** and enter the IP address of the Bindplane agent host.
   - **Server Port** : Enter `514` (or the port configured in the Bindplane agent).
   - **Protocol** : Select **UDP**.
5. Under **Security Logs** , select the log types to forward:
   - **Threat**: Threat detection logs.
   - **DNS**: DNS security logs.
   - **URL**: URL filtering logs.
6. Click **Save**.
7. Assign the syslog profile to the desired ION devices through the device configuration.
8. Verify that syslog messages are being received by checking the Bindplane agent logs.

   > [!NOTE]
   > **Note:** Syslog profiles allow you to apply the same syslog configuration across multiple ION devices. For more information, see [Prisma SD-WAN syslog documentation](https://docs.paloaltonetworks.com/prisma-sd-wan/administration/prisma-sd-wan-sites-and-devices/use-external-services-for-monitoring/syslog-server-support-in-prisma-sd-wan).

## UDM mapping table

| Log Field | UDM Mapping | Logic |
|---|---|---|
| `_about` | `about` | Merged |
| `_intermediary` | `intermediary` | Merged |
| `MSG` | `metadata.description` | Directly mapped |
| `CODE` | `metadata.product_event_type` | Directly mapped |
| `FACILITY` | `metadata.product_event_type` | Directly mapped |
| `log_type` | `metadata.product_event_type` | Directly mapped |
| `APP_NAME` | `network.http.user_agent` | Directly mapped |
| `PROTOCOL_NAME` | `network.ip_protocol` | Directly mapped |
| `BYTES_RECVD` | `network.received_bytes` | Directly mapped |
| `BYTES_SENT` | `network.sent_bytes` | Directly mapped |
| `CLOUDGENIX_HOST` | `principal.hostname` | Directly mapped |
| `ION_HOST` | `principal.hostname` | Directly mapped |
| `NAME` | `principal.hostname` | Directly mapped |
| `SRC_INTERFACE` | `principal.hostname` | Directly mapped |
| `SRC_IP` | `principal.ip` | Merged |
| `src_ip` | `principal.ip` | Merged |
| `SRC_PORT` | `principal.port` | Directly mapped |
| `PROCESS_NAME` | `principal.process.file.full_path` | Directly mapped |
| `pid` | `principal.process.pid` | Directly mapped |
| `sec_result` | `security_result` | Merged |
| `DST_INTERFACE` | `target.hostname` | Directly mapped |
| `REMOTE_HOSTNAME` | `target.hostname` | Directly mapped |
| `DST_IP` | `target.ip` | Merged |
| `REMOTE_IP` | `target.ip` | Merged |
| `dest_ip` | `target.ip` | Merged |
| `DST_PORT` | `target.port` | Directly mapped |
| `VPN_LINK_ID` | `target.resource.id` | Directly mapped |
| N/A | `about` | Constant: `_about` |
| N/A | `intermediary` | Constant: `_intermediary` |
| N/A | `metadata.event_type` | Constant: `GENERIC_EVENT` |
| N/A | `metadata.product_name` | Constant: `CloudGenix SD-WAN` |
| N/A | `metadata.vendor_name` | Constant: `Palo Alto Networks` |
| N/A | `network.received_bytes` | Constant: `uinteger` |
| N/A | `network.sent_bytes` | Constant: `uinteger` |
| N/A | `principal.ip` | Constant: `src_ip` |
| N/A | `security_result` | Constant: `sec_result` |
| N/A | `target.ip` | Constant: `REMOTE_IP` |

## Change Log

[View the Change Log for this parser](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/cloudgenix-sdwan-changelog)

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)