Collect Omnissa Horizon (formerly VMware Horizon) logs

Supported in:

Google secops SIEM

This document explains how to ingest Omnissa Horizon (formerly known as VMware Horizon) logs to Google Security Operations using Bindplane.

Omnissa Horizon is a virtual desktop infrastructure (VDI) platform that delivers virtual desktops and applications to end users. It provides centralized management of virtual machines, session monitoring, and policy enforcement across on-premises and hybrid cloud environments. The parser extracts fields from raw syslog messages using regular expressions (grok patterns) and maps them to the Unified Data Model (UDM).

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 Omnissa Horizon Connection Server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the Omnissa Horizon Console (administrator role)

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](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](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 Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

Linux:

sudo nano /etc/bindplane-agent/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:
    udplog:
        listen_address: "0.0.0.0:514"

exporters:
    chronicle/vmware_horizon:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: VMWARE_HORIZON
        raw_log_field: body

service:
    pipelines:
        logs/vmware_horizon_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/vmware_horizon

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- listen_address: IP address and port to listen on:
  - 0.0.0.0 to listen on all interfaces (recommended)
  - Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)
Exporter configuration:
- 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 copied from the Google SecOps console
- 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

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.
Verify the service is running:
```
sc query observiq-otel-collector
```

Check logs for errors:

type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"

Configure syslog forwarding in Omnissa Horizon (formerly VMware Horizon)

Sign in to the Omnissa Horizon Console with an administrator account.
Go to Settings > Event Configuration.
In the Send to syslog servers section, click Add.
Provide the following configuration details:
- Server Address: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
- Port: Enter 514.
- Protocol: Select UDP.
Click Save.
Verify that events are being forwarded by checking the Bindplane agent logs.

Note: Omnissa Horizon forwards Connection Server events, agent events, administrator audit events, and alarm events through syslog. All event categories are included by default when syslog forwarding is enabled.

UDM mapping table

Log Field	UDM Mapping	Logic
`ActionId`	`metadata.product_log_id`	The value of `ActionId` from the raw log is mapped to `metadata.product_log_id`.
`admin_domain`	`principal.administrative_domain`	The value of `admin_domain` from the raw log is mapped to `principal.administrative_domain`.
`BrokerName`	`principal.hostname`	The value of `BrokerName` from the raw log is mapped to `principal.hostname`.
`BrokerSessionId`	`network.session_id`	The value of `BrokerSessionId` from the raw log is mapped to `network.session_id`.
`ClientIpAddress`	`principal.ip`	The value of `ClientIpAddress` from the raw log is mapped to `principal.ip`.
`CurrentSessionLength`	`network.session_duration.seconds`	The value of `CurrentSessionLength` from the raw log is converted to integer and then mapped to `network.session_duration.seconds`.
`description`	`metadata.description`	The value of `description` from the raw log is mapped to `metadata.description`.
`DesktopDisplayName`	`principal.hostname`	The value of `DesktopDisplayName` from the raw log is mapped to `principal.hostname`.
`EventType`	`metadata.product_event_type`	The value of `EventType` from the raw log is mapped to `metadata.product_event_type`.
`ForwardedClientIpAddress`	`principal.nat_ip`	The value of `ForwardedClientIpAddress` from the raw log is mapped to `principal.nat_ip`.
`GlobalEntitlementName`	`target.user.group_identifiers`	The value of `GlobalEntitlementName` from the raw log is mapped to `target.user.group_identifiers`.
`host`	`principal.hostname`	The value of `host` from the raw log is mapped to `principal.hostname`.
`MachineDnsName`	`principal.url`	The value of `MachineDnsName` from the raw log is mapped to `principal.url`.
`MachineName`	`intermediary.hostname`	The value of `MachineName` from the raw log is mapped to `intermediary.hostname`.
`Module`	`additional.fields`	The key "Module" with the value of `Module` from the raw log is added to `additional.fields` array.
`pid`	`principal.process.pid`	The value of `pid` from the raw log is mapped to `principal.process.pid`.
`PoolId`	`additional.fields`	The key "PoolId" with the value of `PoolId` from the raw log is added to `additional.fields` array.
`program`	`principal.application`	The value of `program` from the raw log is mapped to `principal.application`.
`SessionType`	`additional.fields`	The key "SessionType" with the value of `SessionType` from the raw log is added to `additional.fields` array.
`Severity`	`security_result.severity`	The value of `Severity` from the raw log is uppercased, mapped to generic severities and then mapped to `security_result.severity`.
`timestamp`	`metadata.event_timestamp`	The value of `timestamp` from the raw log is converted to the appropriate format and then mapped to `metadata.event_timestamp`.
`UserDisplayName`	`target.user.user_display_name`	The value of `UserDisplayName` from the raw log is mapped to `target.user.user_display_name`.
`UserName`	`target.user.userid`	The value of `UserName` from the raw log is mapped to `target.user.userid`.
`UserSID`	`target.user.windows_sid`	The value of `UserSID` from the raw log is mapped to `target.user.windows_sid`.
`ViewApiMethodName`	`additional.fields`	The key "ViewApiMethodName" with the value of `ViewApiMethodName` from the raw log is added to `additional.fields` array.
`ViewApiServiceName`	`additional.fields`	The key "ViewApiServiceName" with the value of `ViewApiServiceName` from the raw log is added to `additional.fields` array.
	`extensions.auth.type`	The value is set to "SSO" if the `EventType` field is one of "ADMIN_USERLOGGEDOUT", "AGENT_CONNECTED", "AGENT_DISCONNECTED", "AGENT_ENDED", "AGENT_PENDING", "AGENT_PENDING_EXPIRED", "AGENT_RECONNECTED", "BROKER_DESKTOP_REQUEST", "BROKER_LMV_REMOTE_POD_DESKTOP_LAUNCH", "BROKER_MACHINE_ALLOCATED", "BROKER_USER_AUTHFAILED_BAD_USER_PASSWORD", "BROKER_USER_LOCK_SSO", "BROKER_USERLOGGEDIN", "BROKER_USERLOGGEDOUT", "VLSI_USERLOGGEDIN", "VLSI_INSUFFICIENT_PERMISSION", "VLSI_USERLOGGEDIN_REST", "TIMING_PROFILER_TUNNEL_CONNECTION", "TIMING_PROFILER_GET_LAUNCH_ITEMS", "TIMING_PROFILER_USER_AUTHENTICATION".
	`metadata.event_type`	The value is determined by the `EventType` field. If `EventType` is one of "ADMIN_USERLOGGEDOUT", "AGENT_DISCONNECTED", "AGENT_ENDED", "AGENT_PENDING_EXPIRED", "BROKER_USER_LOCK_SSO", "BROKER_USERLOGGEDOUT" then `metadata.event_type` is "USER_LOGOUT". If `EventType` is one of "AGENT_CONNECTED", "AGENT_PENDING", "AGENT_RECONNECTED", "BROKER_USERLOGGEDIN", "VLSI_USERLOGGEDIN", "VLSI_INSUFFICIENT_PERMISSION", "VLSI_USERLOGGEDIN_REST" then `metadata.event_type` is "USER_LOGIN". If `EventType` is "TIMING_PROFILER_GET_LAUNCH_ITEMS" then `metadata.event_type` is "STATUS_UNCATEGORIZED". If `EventType` is "AGENT_SHUTDOWN" then `metadata.event_type` is "STATUS_SHUTDOWN". If `EventType` is one of "AGENT_STARTUP", "BROKER_LMV_REMOTE_POD_DESKTOP_LAUNCH" then `metadata.event_type` is "STATUS_STARTUP". Otherwise, `metadata.event_type` is "GENERIC_EVENT".
	`metadata.log_type`	The value is set to "VMWARE_HORIZON".
	`metadata.product_name`	The value is set to "HORIZON".
	`metadata.vendor_name`	The value is set to "VMWARE".

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