# Collect Broadcom Support Portal Audit logs

**Parser Version:** 2.0
Supported in:

This document explains how to ingest Broadcom Support Portal Audit logs to Google Security Operations using Bindplane agent.

Broadcom Support Portal provides centralized access to support resources, case management, and product downloads for Broadcom enterprise products. The platform generates audit logs that capture user authentication events, job execution activities, resource access, and administrative operations across the portal infrastructure.

## Before you begin

Make sure you have the following prerequisites:

- A Google SecOps instance
- Windows Server 2016 or later, or Linux host with `systemd`
- Network connectivity between the Bindplane agent and the Broadcom Support Portal infrastructure
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
- Administrative access to the Broadcom Support Portal with permissions to configure syslog forwarding

## 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.

   > [!NOTE]
   > **Note:** The `customer ID` is required for configuring the Bindplane agent exporter.

## 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 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

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

       receivers:
         udplog:
           listen_address: "0.0.0.0:514"

       exporters:
         chronicle/broadcom:
           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: 'your-customer-id'
           endpoint: chronicle.googleapis.com
           log_type: BROADCOM_SUPPORT_PORTAL
           raw_log_field: body

       service:
         pipelines:
           logs/broadcom_to_chronicle:
             receivers:
               - udplog
             exporters:
               - chronicle/broadcom

2. Replace the following placeholders:

- Receiver configuration:

  - `listen_address`: IP address and port to listen on:

    - `0.0.0.0:514` to listen on all interfaces on port 514 (requires root on Linux)
    - `0.0.0.0:1514` to listen on an unprivileged port (recommended for Linux non-root)
  - Receiver type options:

    - `udplog` for UDP syslog (default)
    - `tcplog` for TCP syslog
- 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`: Your `customer ID`. For details, see [Get Google SecOps customer ID](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/broadcom-support-portal#get_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/broadcom:
          compression: gzip
          creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
          customer_id: 'your-customer-id'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: BROADCOM_SUPPORT_PORTAL
          raw_log_field: body

> [!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:

  1. Run the following command:

         sudo systemctl restart observiq-otel-collector

  2. Verify the service is running:

         sudo systemctl status observiq-otel-collector

  3. Check logs for errors:

         sudo journalctl -u observiq-otel-collector -f

<!-- -->

- To restart the Bindplane agent in Windows:

  1. Choose one of the following options:

     - Command Prompt or PowerShell as administrator:

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

     - Services console:

       1. Press `Win+R`, type `services.msc`, and press Enter.
       2. Locate **observIQ OpenTelemetry Collector**.
       3. Right-click and select **Restart**.
  2. Verify the service is running:

         sc query observiq-otel-collector

  3. Check logs for errors:

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

## Configure Broadcom Support Portal syslog forwarding

Broadcom Support Portal can forward audit log events via syslog to external collectors for SIEM integration.

### Configure remote syslog logging

1. Sign in to the **Broadcom Support Portal** administration console.
2. Go to **Administration \> Logs \> Remote Logging**.
3. Enable **Remote Syslog**.
4. Configure the following syslog parameters:

   - **Syslog Server Address** : Enter the IP address or hostname of the Bindplane agent host (for example, `192.168.1.100`).
   - **Port** : Enter the port matching the Bindplane agent `listen_address` (for example, `514`).
   - **Protocol** : Select **UDP** (default) or **TCP** to match the Bindplane agent receiver type.
5. Click **Save**.

### Select audit event categories

1. In the **Remote Logging** configuration, select the audit event categories to forward:

   - **User authentication events**: Login and logout activities
   - **Job events**: Job execution status and state changes
   - **Resource access events**: Access to support resources and downloads
   - **Administrative events**: Configuration changes and administrative operations
2. Click **Save**.

   > [!NOTE]
   > **Note:** Specific event categories and configuration options depend on your Broadcom Support Portal deployment and license level. Refer to the Broadcom Support Portal documentation for your specific version.

### Verify syslog forwarding

1. After saving the syslog configuration, perform a test action in the Broadcom Support Portal (for example, sign in or access a resource).
2. Check the Bindplane agent logs for incoming syslog messages:

   - **Linux** : `sudo journalctl -u observiq-otel-collector -f`
   - **Windows** : `type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"`
3. Verify that audit log messages appear in the logs.

## UDM mapping table

| Log Field | UDM Mapping | Logic |
|---|---|---|
| ParallelDestination, STORAGE_TYPE, JOB_NAME, kubernetes.docker_id, kubernetes.pod_id | target.resource.attribute.labels | Merged with corresponding labels |
| destinationName, responseDestinationName, DESTINATION_NAME | target.application | Value from DESTINATION_NAME if not empty, else responseDestinationName if not null or empty, else destinationName |
| kubernetes.container_hash | target.file.full_path | Extracted using grok pattern %{DATA:filepath}:%{GREEDYDATA:file_sha} |
| kubernetes.container_hash | target.file.sha256 | Extracted using grok pattern %{DATA:filepath}:%{GREEDYDATA:file_sha} |
| groupId | target.user.group_identifiers | Merged from groupId |
| dispatch, companyId | additional.fields | Merged with dispatch_label and companyId_label |
| response, responseId | security_result.detection_fields | Merged with response_label and responseId_label |
| kubernetes.container_image, kubernetes.container_name, kubernetes.namespace_name, kubernetes.pod_name | principal.resource.attribute.labels | Merged with corresponding labels |
| GROUP_NAME | principal.group.group_display_name | Value copied directly |
| kubernetes.host | principal.asset.hostname | Value copied directly |
| kubernetes.host | principal.hostname | Value copied directly |
| payload | principal.resource.product_object_id | Value copied directly |
| severity | security_result.severity | Uppercased and set if in allowed list |
| description, JOB_STATE | security_result.description | Value from description if not empty, else JOB_STATE |
| timestramp | metadata.event_timestamp | Parsed using ISO8601, yyyy-MM-ddTHH:mm:ss.SSSSSSSSSZ, yyyy-MM-dd HH:mm:ss.SSS formats |
|   | metadata.event_type | Set to "USER_LOGIN" if has_principal, has_target, user_login; "USER_LOGOUT" if has_principal, has_target, user_logout; "STATUS_UPDATE" if has_principal; else "GENERIC_EVENT" |
|   | extensions.auth.type | Set to "AUTHTYPE_UNSPECIFIED" if user login or logout event |
|   | metadata.product_name | Set to "BROADCOM_SUPPORT_PORTAL" |
|   | metadata.vendor_name | Set to "BROADCOM_SUPPORT_PORTAL" |
| `module` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `socket_details` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `fd` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `family` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `type` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `level` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `log_data` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `timestamp_details` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `session_duration` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `correlationId` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `className` | `event.idm.read_only_udm.additional.fields` | Mapped from changelog |
| `proto` | `event.idm.read_only_udm.network.ip_protocol` | Mapped from changelog |
| `request_url_details` | `event.idm.read_only_udm.network.http.referral_url` | Mapped from changelog |
| `log_level` | `event.idm.read_only_udm.security_result.severity` | Mapped from changelog |
| `log_level` | `event.idm.read_only_udm.security_result.severity_details` | Mapped from changelog |
| `principal_userId_details` | `event.idm.read_only_udm.principal.user.userid` | Mapped from changelog |
| `target_url_details` | `event.idm.read_only_udm.target.url` | Mapped from changelog |
| `url_details` | `event.idm.read_only_udm.target.url` | Mapped from changelog |
| `desc` | `event.idm.read_only_udm.metadata.description` | Mapped from changelog |
| `user_email` | `event.idm.read_only_udm.principal.user.email_addresses` | Mapped from changelog |
| `principal_application` | `event.idm.read_only_udm.principal.application` | Mapped from changelog |
| `principal_ip` | `event.idm.read_only_udm.principal.ip` and `event.idm.read_only_udm.principal.asset.ip` | Mapped from changelog |
| `method_details` | `event.idm.read_only_udm.network.http.method` | Mapped from changelog |
| `application_protocol_details` | `event.idm.read_only_udm.network.application_protocol_version` | Mapped from changelog |
| `application_protocol_data` | `event.idm.read_only_udm.network.application_protocol` | Mapped from changelog |
| `response_code_details` | `event.idm.read_only_udm.network.http.response_code` | Mapped from changelog |
| `received_bytes_details` | `event.idm.read_only_udm.network.received_bytes` | Mapped from changelog |
| `sent_byte_details` | `event.idm.read_only_udm.network.sent_bytes` | Mapped from changelog |
| `user_agent_details` | `event.idm.read_only_udm.network.http.user_agent` | Mapped from changelog |
| `user_agent_details` | `event.idm.read_only_udm.network.http.parsed_user_agent` | Mapped from changelog |
| `target_ip` | `event.idm.read_only_udm.target.ip` and `event.idm.read_only_udm.target.asset.ip` | Mapped from changelog |
| `target_port` | `event.idm.read_only_udm.target.port` | Mapped from changelog |
| `principal_port` | `event.idm.read_only_udm.principal.port` | Mapped from changelog |
| `product_log_id_details` | `event.idm.read_only_udm.metadata.product_log_id` | Mapped from changelog |
| `application_details` | `event.idm.read_only_udm.target.application` | Mapped from changelog |

## Change Log

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

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