Collect BeyondTrust Secure Remote Access (formerly BeyondTrust Privileged Remote Access) logs

This document explains how to ingest BeyondTrust Secure Remote Access (formerly known as BeyondTrust Privileged Remote Access) logs to Google Security Operations using Bindplane.

BeyondTrust Secure Remote Access is a privileged access management solution that lets organizations control, monitor, and audit privileged remote access for vendors, contractors, and internal administrators connecting to critical systems. It provides credential injection, just-in-time access, and session recording. BeyondTrust Secure Remote Access logs session activity, authentication events, and administrative actions via syslog.

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.
• Administrative access to the BeyondTrust Secure Remote Access B Series Appliance interface (/appliance).

Get Google SecOps ingestion authentication file

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Collection Agent.
3. Download the Ingestion Authentication File.
   • Save the file securely on the system where Bindplane will be installed.

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 this installation guide.

Configure the Bindplane agent to ingest Syslog and send to Google SecOps

1. Access the Configuration File:

   • Locate the config.yaml file. Typically, it's in the /opt/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:
       udplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:514"
   
   exporters:
       chronicle/chronicle_w_labels:
           compression: gzip
           # Adjust the path to the credentials file you downloaded in Step 1
           creds_file_path: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: <your_customer_id>
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           log_type: 'BEYONDTRUST_REMOTE_ACCESS'
           raw_log_field: body
           ingestion_labels:
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

• Replace the port and IP address as required in your infrastructure.
• Replace <your_customer_id> with the actual Customer ID.

• Update /path/to/ingestion-authentication-file.json to the file path where the authentication file was saved in Step 1.

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 BeyondTrust Secure Remote Access syslog forwarding

1. Sign in to the BeyondTrust Secure Remote Access B Series Appliance interface (/appliance).
2. Go to Security > Appliance Administration.
3. Scroll down to the Syslog section.
4. In the Remote Syslog Server field, enter the hostname or IP address of the Bindplane agent host (for example, 192.168.1.100).
5. Select the Message Format for event notification messages:
   • RFC 5424 - modern syslog standard with structured data (recommended).
   • BSD (legacy) - legacy BSD syslog format (RFC 3164).
   • Syslog over TLS - encrypted syslog using TCP port 6514.
6. If necessary, change the default port:
   • RFC 5424 and BSD formats default to UDP 514.
   • Syslog over TLS defaults to TCP 6514.

7. Click Save.

Verify syslog delivery

1. After configuring syslog forwarding, initiate a test support session or sign in to the /login administrative interface.

2. On the Bindplane agent host, verify that logs are being received:

   sudo journalctl -u observiq-otel-collector -f
   

For more information, see the BeyondTrust Privileged Remote Access syslog documentation.

UDM mapping table

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