Collect Broadcom CA PAM logs

Parser Version: 1.0

Supported in:

Google SecOps SIEM

This document explains how to ingest Broadcom CA Privileged Access Manager logs to Google Security Operations using Bindplane. Broadcom CA Privileged Access Manager (PAM) is an enterprise privileged access management solution that controls, monitors, and audits privileged user access to critical systems. It provides credential vaulting, session recording, and access policy enforcement across hybrid environments.

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 Broadcom Privileged Access Management web UI.

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 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: 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 SIEM 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: 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 SIEM 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 the 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
   

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
   

Additional installation resources

For additional installation options, consult the installation guide.

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

1. Access the configuration file:

   • Locate the config.yaml file. Typically, it is in the /observiq-otel-collector/ directory on Linux or in the installation directory on Windows.
   • Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

   receivers:
     tcplog:
       listen_address: "0.0.0.0:514"
   
   exporters:
     chronicle/broadcom_ca_pam:
       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: '/path/to/ingestion-authentication-file.json'
       customer_id: '<customer_id>'
       endpoint: chronicle.googleapis.com
       log_type: BROADCOM_CA_PAM
       raw_log_field: body
       ingestion_labels:
   
   service:
     pipelines:
       logs/broadcom_ca_pam:
         receivers:
           - tcplog
         exporters:
           - chronicle/broadcom_ca_pam
   

• Replace the port and IP address as required in your infrastructure.
• 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.
• Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
• Replace <customer_id> with the actual customer ID.
• Update /path/to/ingestion-authentication-file.json to the path where the service account key file (Option 1) was saved in the Get Google SecOps credentials for the Bindplane agent section.

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 (for example, europe-malachiteingestion-pa.googleapis.com).

  exporters:
    chronicle/broadcom_ca_pam:
      compression: gzip
      creds_file_path: '/path/to/ingestion-authentication-file.json'
      customer_id: '<customer_id>'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: BROADCOM_CA_PAM
      raw_log_field: body
      ingestion_labels:
  

Note: This exporter will stop working when the Ingestion API is discontinued on July 20, 2027.

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 remote syslog on Broadcom CA PAM

1. Sign in to the Privileged Access Management web UI.
2. Go to Configuration > Logs > Syslog.
3. Select the Syslog Enabled toggle.
4. Select Space Delimited from the Message Format list.
5. Click Add Server.

6. Provide the following configuration details in the new row:

   • Server: Enter the Bindplane agent IP address (for example, 192.168.1.100).
   • Port: Enter 514 (or your configured Bindplane agent port). If you leave the port blank, it defaults to 514.
   • Protocol: Select TCP.
   Note: If you select TCP, the TLS option becomes available. Enable TLS if your environment requires encrypted syslog transport.

7. Click Update to save the settings.

8. Verify that logs are being sent by checking the Bindplane agent logs.

UDM mapping table

Log Field	UDM Mapping	Logic
UserGroup_label	additional.fields	Merged
access_protocol	metadata.access_protocol	Directly mapped
Details	metadata.description	Directly mapped
has_principal	metadata.event_type	Mapped: true → SCAN_UNCATEGORIZED, true → STATUS_UPDATE
has_user	metadata.event_type	Mapped: true → USER_UNCATEGORIZED
host	principal.asset.hostname	Directly mapped
host	principal.hostname	Directly mapped
NatIP	principal.nat_ip	Merged
Port	principal.port	Directly mapped
pid	principal.process.pid	Directly mapped
DeviceName	principal.resource.name	Directly mapped
User	principal.user.userid	Directly mapped
sec_res	security_result	Merged
detection_fields	security_result.detection_fields	Merged
Service_App	target.application	Directly mapped
Address	target.asset.hostname	Directly mapped
Address	target.hostname	Directly mapped
N/A	metadata.event_type	Constant: SCAN_UNCATEGORIZED
N/A	metadata.product_name	Constant: Broadcom CA Pam
N/A	metadata.vendor_name	Constant: Broadcom

Change Log

View the Change Log for this parser

Need more help? Get answers from Community members and Google SecOps professionals.