Collect ION Spectrum logs

Supported in:

Google secops SIEM

This document explains how to ingest ION Spectrum logs to Google Security Operations using the Bindplane agent.

ION Spectrum is a financial trading and processing platform from ION Group, used for FX and multi-asset front/middle/back-office automation. It generates audit logs for trading activity, system events, and user operations.

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 ION Spectrum server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the ION Spectrum server with administrator permissions

Get Google SecOps ingestion authentication file

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

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

Get Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
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 or Linux operating system according to the following instructions.

Windows installation

Open Command Prompt or PowerShell as an administrator.

Run the following command:

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

Wait for the installation to complete.
Verify the installation by running:
```
sc query observiq-otel-collector
```
The service should show as RUNNING.

Linux installation

Open a terminal with root or sudo privileges.

Run the following command:

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

Wait for the installation to complete.
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 the Bindplane agent installation guide.

Configure the Bindplane agent to ingest logs 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:
    filelog:
        include:
            - /opt/ion/spectrum/logs/*.csv
            - /opt/ion/spectrum/logs/*.log
        start_at: beginning
        poll_interval: 5s

exporters:
    chronicle/ion_spectrum:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: ION_SPECTRUM
        raw_log_field: body
        ingestion_labels:
            env: production

service:
    pipelines:
        logs/ion_spectrum_to_chronicle:
            receivers:
                - filelog
            exporters:
                - chronicle/ion_spectrum

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- include: Paths to ION Spectrum log files:
  - Windows: C:\ION\Spectrum\logs\*.csv and C:\ION\Spectrum\logs\*.log
  - Linux: /opt/ion/spectrum/logs/*.csv and /opt/ion/spectrum/logs/*.log
- start_at: Set to beginning to read existing logs, or end to read only new entries
- poll_interval: How often to check for new log data (default: 5s)
Exporter configuration:
- ion_spectrum: Descriptive name for the exporter
- creds_file_path: Full path to ingestion authentication file:
  - Linux: /etc/bindplane-agent/ingestion-auth.json
  - Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- <customer_id>: Customer ID from the previous step
- endpoint: Regional endpoint URL:
  - US: malachiteingestion-pa.googleapis.com
  - Europe: europe-malachiteingestion-pa.googleapis.com
  - Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
  - See Regional Endpoints for complete list
- ION_SPECTRUM: Log type exactly as it appears in Chronicle
- ingestion_labels: Optional labels in YAML format (for example, env: production)
Pipeline configuration:
- ion_spectrum_to_chronicle: Descriptive name for the pipeline

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

Verify the service is running:

sudo systemctl status observiq-otel-collector

Check logs for errors:

sudo journalctl -u observiq-otel-collector -f

To restart the Bindplane agent in Windows, 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.
  4. Verify the service is running:
```
sc query observiq-otel-collector
```
  5. Check logs for errors:
```
type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"
```

Configure ION Spectrum log collection

Sign in to the ION Spectrum server with administrator privileges.
Navigate to the ION Spectrum log directory. Common default paths include:
- Windows: C:\ION\Spectrum\logs\
- Linux: /opt/ion/spectrum/logs/
Verify that the following log types are being generated:
- Audit logs: User activity, login/logout events, and configuration changes (CSV format).
- Transaction logs: Trade execution, order management, and settlement events.
- System logs: Application errors, warnings, and performance events.
Ensure the Bindplane agent has read permissions on the log directory and files.
If the Bindplane agent runs on a different host than ION Spectrum, configure a network file share (NFS or SMB) to make the log directory accessible to the Bindplane agent host.

Note: The exact log directory depends on your ION Spectrum deployment configuration. Consult your ION Group deployment guide or account representative for the specific log file locations.

UDM mapping table

Log Field	UDM Mapping	Logic
column5	metadata.event_timestamp	Timestamp when the event occurred
has_principal, has_target_user, column6	metadata.event_type	Type of event (for example, USER_LOGIN, NETWORK_CONNECTION)
column6	metadata.product_event_type	Type of event as defined by the product
column1	principal.asset.hostname	Hostname of the asset associated with the principal
column1	principal.asset.ip	IP address of the asset associated with the principal
column1	principal.hostname	Hostname associated with the principal
column1	principal.ip	IP address associated with the principal
column7	security_result.action	Action taken as a result of the security evaluation
column7	security_result.action_details	Details about the security result action
column4	target.user.group_identifiers	Identifiers for groups the target user belongs to
column3	target.user.user_display_name	Display name of the target user
column2	target.user.userid	User ID of the target user
	metadata.product_name	Name of the product that generated the event
	metadata.vendor_name	Name of the vendor that generated the event

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