Collect Veeam logs

Supported in:

Google secops SIEM

This document explains how to ingest Veeam logs to Google Security Operations using Bindplane. The parser extracts fields from the syslog messages using grok patterns, performs data transformations like replacing and merging fields, and maps the extracted data to the Unified Data Model (UDM) based on event type and available fields. It also handles error conditions and sets appropriate severity levels.

Before you begin

Make sure you have the following prerequisites:

Google SecOps instance
Windows 2016 or later or a Linux host with systemd
If running behind a proxy, ensure firewall ports are open
Privileged access to Veeam

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.

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.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

Open the 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

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

Additional installation resources

For additional installation options, consult the installation guide.

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

Access the configuration file:
- Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
- Open the file using a text editor (for example, nano, vi, or Notepad).

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: <customer_id>
        endpoint: malachiteingestion-pa.googleapis.com
        # Add optional ingestion labels for better organization
        log_type: 'VEEAM'
        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 <customer_id> with the actual customer ID.
Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

To restart the Bindplane agent in Linux, run the following command:
```
sudo systemctl restart bindplane-agent
```
To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:
```
net stop BindPlaneAgent && net start BindPlaneAgent
```

Configure Syslog for Veeam

Sign in to the Veeam Backup & Replication console.
Go to Menu > Options > SIEM Integrations.
On the Syslog servers section, click Add.
Provide the following configuration details:
- Name: Enter the Bindplane agent IP address and port number (for example, 192.168.1.1:514).
- Transport: Select UDP or TCP, depending on your actual Bindplane agent configuration.
Click OK to save.

UDM Mapping Table

Log Field	UDM Mapping	Logic
`application`	`principal.application`	Directly mapped from the `application` field extracted by the grok pattern.
`CredentialId`	`principal.resource.attribute.labels.[]`	Directly mapped from the `CredentialId` field extracted by the kv filter. A label with key "CredentialId" is created.
`date_2`, `time_2`, `year`	`metadata.event_timestamp`	The `date_2`, `time_2`, and `year` fields are concatenated and parsed using the `date` filter to create the `metadata.event_timestamp`.
`date_2`, `time_2`	`metadata.event_timestamp`	The `date_2` and `time_2` fields are concatenated and parsed using the `date` filter to create the `metadata.event_timestamp`.
`deviceId`	`principal.resource.product_object_id`	Directly mapped from the `deviceId` field extracted by the kv filter.
`description`	`security_result.description`	Directly mapped from the `description` field extracted by the grok pattern.
`error_code`	`security_result.detection_fields.[]`	Directly mapped from the `error_code` field extracted by the grok pattern. A label with key "error_code" is created.
`executing_feature`	`principal.hostname`, `principal.asset.hostname`	Directly mapped from the `executing_feature` field extracted by the grok pattern.
`host`	`principal.hostname`, `principal.asset.hostname`	Directly mapped from the `host` field extracted by the grok pattern.
`ManagementIP`	`principal.ip`, `principal.asset.ip`	Directly mapped from the `ManagementIP` field extracted by the kv filter.
`pid`	`principal.process.pid`	Directly mapped from the `pid` field extracted by the grok pattern.
`previousSeverity`	`security_result.severity_details`	Directly mapped from the `previousSeverity` field extracted by the grok pattern.
`prod_event_type`	`metadata.product_event_type`	Directly mapped from the `prod_event_type` field extracted by the grok pattern.
`query`	`security_result.detection_fields.[]`	Directly mapped from the `query` field extracted by the grok pattern. A label with key "query" is created.
`reportingAddress`	`principal.ip`, `principal.asset.ip`	Directly mapped from the `reportingAddress` field extracted by the grok pattern.
`severity`	`security_result.severity`	Mapped from the `severity` field. The value is determined by conditional logic based on the `severity` field (ERROR, MAJOR/WARN, INFO map to specific UDM severity values).
`src_ip`	`principal.ip`, `principal.asset.ip`	Directly mapped from the `src_ip` field extracted by the grok pattern.
`summary`	`security_result.summary`	Directly mapped from the `summary` field extracted by the grok pattern.
`target_ip`	`target.ip`, `target.asset.ip`	Directly mapped from the `target_ip` field extracted by the grok pattern.
`thread_id`	`security_result.detection_fields.[]`	Directly mapped from the `thread_id` field extracted by the grok pattern. A label with key "thread_id" is created.
(N/A)	`event_type`	Determined by logic in the parser. If both `principal` and `target` have MID data present, it's `NETWORK_UNCATEGORIZED`. If only `principal` has MID data, it's `STATUS_UPDATE`. Otherwise, it's `GENERIC_EVENT`.
(N/A)	`metadata.event_type`	Copied from the internally generated `event_type` field.
(N/A)	`metadata.vendor_name`	Hardcoded to "VEEAM".
(N/A)	`metadata.product_name`	Hardcoded to "Veeam".
(N/A)	`event.timestamp`	The event timestamp is taken from the Log Entry's `collection_time` field.

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