Collect SOTI MobiControl logs

This document explains how to ingest SOTI MobiControl logs to Google Security Operations using the Bindplane agent.

SOTI MobiControl is an enterprise mobility management (EMM) platform for device management, security, and application deployment. It supports native syslog forwarding for device events, administrative actions, and security alerts.

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 SOTI MobiControl server
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the SOTI MobiControl administration console

Get Google SecOps ingestion authentication file

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 Bindplane will be installed.

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 IDfrom the Organization Detailssection.

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 Promptor PowerShellas 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 the Bindplane agent installation guide .

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 
   : 
    
   udplog 
   : 
    
   listen_address 
   : 
    
   "0.0.0.0:514" 
   exporters 
   : 
    
   chronicle/soti_mobicontrol 
   : 
    
   compression 
   : 
    
   gzip 
    
   creds_file_path 
   : 
    
   '/etc/bindplane-agent/ingestion-auth.json' 
    
   customer_id 
   : 
    
   '<customer_id>' 
    
   endpoint 
   : 
    
   malachiteingestion-pa.googleapis.com 
    
   log_type 
   : 
    
   SOTI_MOBICONTROL 
    
   raw_log_field 
   : 
    
   body 
   service 
   : 
    
   pipelines 
   : 
    
   logs/soti_mobicontrol_to_chronicle 
   : 
    
   receivers 
   : 
    
   - 
    
   udplog 
    
   exporters 
   : 
    
   - 
    
   chronicle/soti_mobicontrol 
   
  

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

  1. Verify the service is running:

      sudo  
     systemctl  
     status  
     observiq-otel-collector 
     

  2. 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 SOTI MobiControl syslog forwarding

1. Sign in to the SOTI MobiControladministration console.
2. Go to Global Settings > System Configuration > Syslog.
3. Configure the syslog destination:
   • Syslog Server: Enter the IP address of the Bindplane agent host.
   • Port: Enter 514 .
   • Protocol: Select UDP.
   • Facility: Select the syslog facility (for example, Local0).
4. Select the log categories to forward:
   • Device Events: Enrollment, check-in, compliance, and alert events.
   • Administrative Events: User logins, policy changes, and configuration modifications.
   • Security Events: Wipe commands, lock events, and policy violations.
5. Click Save.

UDM mapping table

Log Field	UDM Mapping	Logic
source	additional.fields	Merged with label key="Source", value=source if source != ""
	extensions.auth.type	Set to "AUTHTYPE_UNSPECIFIED" if metadata.event_type == "USER_LOGOUT"
hostname	intermediary.hostname	Value copied directly if hostname != ""
timestamp	metadata.event_timestamp	Parsed from timestamp using ISO8601 format after replacing +.* with Z
target_url, server, device_id, user_name, user_id, user_display_name	metadata.event_type	Set to USER_LOGOUT if target_url != "", else STATUS_UPDATE if any of server, device_id, user_name, user_id, user_display_name != "", else GENERIC_EVENT
server	principal.hostname	Value copied directly if server != ""
device_id	principal.resource.product_object_id	Value copied directly if device_id != ""
user_name, user_display_name	principal.user.user_display_name	Value from user_name if not empty, else from user_display_name if user_display_name != "" and user_name == ""
user_id	principal.user.userid	Value copied directly if user_id != ""
description	security_result.description	Value copied directly if description != ""
severity	security_result.severity	Set to INFORMATIONAL if severity == INFORMATION, MEDIUM if WARNING, severity if ERROR or CRITICAL
severity	security_result.severity_details	Set to severity if severity not in INFORMATION, WARNING, ERROR, CRITICAL
category	security_result.summary	Value copied directly if category != ""
target_url	target.url	Value copied directly if target_url != ""
	metadata.product_name	Set to "SOTI_MOBICONTROL"
	metadata.vendor_name	Set to "SOTI_MOBICONTROL"

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