Collect Verba Recording System logs

Supported in:

Google SecOps SIEM

Note: This feature is covered by Pre-GA Offerings Terms of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the Google SecOps Technical Support Service guidelines and the Google SecOps Service Specific Terms.
If this feature isn't visible in your environment, see Manage preview features or contact your system administrator.

This document explains how to ingest Verba Recording System logs to Google Security Operations using Bindplane.

Verba Recording System (now Verint) is a communications compliance recording platform used for capturing and archiving voice, video, and messaging interactions. The Bindplane agent collects Verba log files directly from the local file system.

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance
• Windows Server 2016 or later with observiq-otel-collector service support
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Verba Recording System server with administrator permissions

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.

   Note: The customer ID is required for configuring the Bindplane agent exporter.

Install the Bindplane agent

Install the Bindplane agent on your Windows 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.

Additional installation resources

For additional installation options and troubleshooting, see Bindplane agent 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 Bindplane agent to ingest logs and send to Google SecOps

Locate the configuration file

• 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:
    filelog:
      include:
        - C:\Program Files\Verba\log\*.log
      start_at: beginning
  
  exporters:
    chronicle/verba_rec:
      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: 'C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: chronicle.googleapis.com
      log_type: VERBA_REC
      raw_log_field: body
      ingestion_labels:
        env: production
  
  service:
    pipelines:
      logs/verba_to_chronicle:
        receivers:
          - filelog
        exporters:
          - chronicle/verba_rec
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • filelog: The receiver type for collecting log files from disk
  • include: List of file paths to monitor. Default Verba Recording System log locations:
    • C:\Program Files\Verba\log\*.log
    • C:\Verba\log\*.log (alternative installation path)
  • start_at: Set to beginning to read existing logs or end to only read new entries

• Exporter configuration:

  • verba_rec: Descriptive name for the exporter
  • creds_file_path: Full path to the service account JSON key file (Option 1):
    • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
  • <customer_id>: Customer ID from the previous step
  • 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 for the complete list.
  • project: Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
  • endpoint: Keep set to chronicle.googleapis.com.
  • VERBA_REC: Log type exactly as it appears in Chronicle
  • ingestion_labels: Optional labels in YAML format (for example, env: production)

• Pipeline configuration:

  • verba_to_chronicle: Descriptive name for the pipeline

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/verba_rec:
      compression: gzip
      creds_file_path: 'C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: VERBA_REC
      raw_log_field: body
      ingestion_labels:
        env: production
  

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:
  • Windows: Click File > Save

Restart the Bindplane agent to apply the changes

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 Verba Recording System logging

Verba Recording System stores audit and compliance recording logs on the application server. You can collect logs from the file system or export them from the web console.

Verify log file locations

1. Sign in to the Verba Recording System server with administrator privileges.

2. Navigate to the Verba log directory. Default locations include:

   • C:\Program Files\Verba\log\
   • `C:\Verba\log` (alternative installation path)
   Note: The exact log path depends on your Verba installation configuration. Consult the Verba Recording System Administration Guide for your version.

3. Ensure the Bindplane agent include path in config.yaml matches the actual log file location on your Verba server.

(Optional) Export audit logs from Verba Web Console

1. Sign in to the Verba Recording System web console as an administrator.
2. Go to System > Logs > Audit Trail.
3. Configure the search parameters:
   • Date Range: Select the start and end dates.
   • Event Category: Select the log categories to export (for example, recording events, user activity, system events, compliance events).
   • User: Optionally filter by specific user.
4. Click Search to retrieve the audit records.
5. Click Export to CSV to download the log data.

6. Save the exported file to the log directory monitored by the Bindplane agent (for example, `C:\Program Files\Verba\log`).

   Note: The Bindplane agent service account must have read access to the Verba log directory.

UDM mapping table

Log Field	UDM Mapping	Logic
column2, column3, column4, column5, column7	metadata.description	Value copied directly if not empty
	metadata.event_type	Set to "USER_UNCATEGORIZED" if column1 or column6 not empty, else "GENERIC_EVENT"
column1	principal.user.userid	Value from column1 after applying regex to remove " \([^)]+\)$" if not empty
column8	security_result.action_details	Value copied directly if not empty
column2, column3, column4, column5, column7	security_result.detection_fields	Merged with label objects created from each column if not empty; each label has key set to specific string (e.g., "Timestamp" for column2) and value copied from column
column9	security_result.summary	Value copied directly if not empty
column6	target.user.userid	Value from column6 after applying regex to remove " \([^)]+\)$" if not empty
	metadata.product_name	Set to "Verba_Recording_Systems"
	metadata.vendor_name	Set to "Verba_Recording_Systems"

Change Log

View the Change Log for this parser

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