Collect Omnissa Workspace ONE UEM (formerly VMware AirWatch) logs

Supported in:

Google SecOps SIEM

This document explains how you can ingest Omnissa Workspace ONE UEM (formerly known as VMware AirWatch) logs to Google Security Operations using Bindplane.

Omnissa Workspace ONE UEM is an enterprise mobility management (EMM) platform that provides unified endpoint management across mobile, desktop, rugged, and IoT devices. It enables IT administrators to enroll, configure, secure, and manage corporate and employee-owned devices from a single console.

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 Omnissa Workspace ONE UEM
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Omnissa Workspace ONE UEM console with administrator role

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 or Linux 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.

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
   

3. Wait for the installation to complete.

4. 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 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 the Bindplane agent to ingest syslog 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:
    tcplog:
      listen_address: "0.0.0.0:514"
  
  exporters:
    chronicle/airwatch:
      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: '<PLACEHOLDER_CREDS_FILE_PATH>'
      customer_id: '<PLACEHOLDER_CUSTOMER_ID>'
      endpoint: chronicle.googleapis.com
      log_type: AIRWATCH
      raw_log_field: body
      ingestion_labels:
        env: production
  
  service:
    pipelines:
      logs/airwatch_to_chronicle:
        receivers:
          - tcplog
        exporters:
          - chronicle/airwatch
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • tcplog: TCP syslog receiver for reliable log delivery from Workspace ONE UEM
  • 0.0.0.0:514: IP address and port to listen on. Replace the port as required in your infrastructure

• Exporter configuration:

  • <PLACEHOLDER_CREDS_FILE_PATH>: Full path to the service account JSON key file (Option 1):
    • Linux: /opt/observiq-otel-collector/ingestion-auth.json
    • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
  • <PLACEHOLDER_CUSTOMER_ID>: Google SecOps customer ID
  • 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.

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/airwatch:
      compression: gzip
      creds_file_path: '<PLACEHOLDER_CREDS_FILE_PATH>'
      customer_id: '<PLACEHOLDER_CUSTOMER_ID>'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: AIRWATCH
      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:
  • 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:

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 syslog forwarding in Omnissa Workspace ONE UEM

1. Sign in to the Omnissa Workspace ONE UEM console.
2. Go to Groups & Settings > All Settings > System > Enterprise Integration > Syslog.
3. Select Override for the Current Setting if inheriting from a parent organization group.
4. Set Syslog Integration to Enabled.
5. Provide the following configuration details:
   • Hostname: Enter the IP address or FQDN of the Bindplane agent host.
   • Protocol: Select TCP.
   • Port: Enter the Bindplane agent port number (for example, 514).
   • Syslog Facility: Leave as default or select the appropriate facility for your environment.
   • Message Tag: Enter Airwatch.
   • Message Content: Leave as default.
6. Go to the Advanced tab.
7. Provide the following configuration details:
   • Console Events: Select Enable.
   • Select Console Events to Send to Syslog: Click Select All.
   • Device Events: Select Enable.
   • Select Device Events to Send to Syslog: Click Select All.
8. Click Save.
9. Click Test Connection to verify that syslog events are being forwarded to the Bindplane agent.

For more information, see Omnissa Workspace ONE UEM Troubleshooting and Logging Guide.

UDM mapping table

Log Field	UDM Mapping	Logic
AdminAccount	principal.user.userid	The value is taken from the AdminAccount field in the raw log.
Application	target.application	The value is taken from the Application field in the raw log.
Event	metadata.product_event_type	The value is taken from the Event field in the raw log.
EventSource	principal.application	The value is taken from the EventSource field in the raw log.
FriendlyName	principal.asset.hostname	The value is taken from the FriendlyName field in the raw log.
GroupName	target.group.group_display_name	The value is taken from the GroupName field in the raw log.
Severity	security_result.severity	Mapped based on severity value: Information maps to INFORMATIONAL, Warning maps to MEDIUM, Critical maps to HIGH.
	metadata.product_name	Set to AIRWATCH.
	metadata.vendor_name	Set to VMware.

Change Log

View the Change Log for this parser

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