Collect Ordr IoT logs

Supported in:

Google SecOps SIEM

This document explains how to ingest Ordr SCE logs to Google Security Operations using Bindplane.

Ordr Systems Control Engine (SCE) is a connected device security platform that provides visibility and threat detection across IoT, OT, and IoMT devices. It supports forwarding security alerts, device events, and alarm data to external SIEM platforms via syslog in CEF (Common Event Format). Ordr was acquired by Palo Alto Networks in 2024.

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 Ordr SCE appliance
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Ordr SCE management console with administrator permissions

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:
    udplog:
      listen_address: "0.0.0.0:514"
  
  exporters:
    chronicle/ordr_iot:
      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: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: chronicle.googleapis.com
      log_type: ORDR_IOT
      raw_log_field: body
      ingestion_labels:
        env: production
  
  service:
    pipelines:
      logs/ordr_to_chronicle:
        receivers:
          - udplog
        exporters:
          - chronicle/ordr_iot
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • udplog: The receiver type based on protocol:
    • udplog for UDP syslog
    • tcplog for TCP syslog
  • 0.0.0.0: IP address to listen on:
    • 0.0.0.0 to listen on all interfaces (recommended)
    • Specific IP address to listen on one interface
  • 514: Port number to listen on (for example, 514, 1514, 6514)

• Exporter configuration:

  • ordr_iot: Descriptive name for the exporter
  • 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
  • <customer_id>: Customer ID from the previous step
  • 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.
  • ORDR_IOT: Log type exactly as it appears in Chronicle
  • ingestion_labels: Optional labels in YAML format (for example, env: production)

• Pipeline configuration:

  • ordr_to_chronicle: Descriptive name for the pipeline

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/ordr_iot:
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: ORDR_IOT
      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 Ordr SCE syslog forwarding

1. Sign in to the Ordr SCE management console with administrator credentials.
2. Go to Settings > Integrations > SIEM.
3. Click Add or Configure to set up a new syslog integration.
4. Provide the following configuration details:
   • Syslog Server IP/Hostname: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
   • Port: Enter 514 (must match the Bindplane agent receiver port).
   • Protocol: Select UDP (must match the Bindplane agent receiver type).
   • Format: Select CEF (Common Event Format).
5. Select the event types to forward (for example, alarms, security events, device classification events).
6. Click Save to apply the configuration.

7. Verify that syslog messages are being received by checking the Bindplane agent logs.

   Note: Ordr SCE also integrates with Splunk, QRadar, and other SIEM platforms directly. Check the Ordr integrations page for platform-specific connectors. Refer to updated Palo Alto Networks documentation for the latest integration options.

UDM mapping table

Log Field	UDM Mapping	Logic
additional_alarmHash, additional_connectionState, additional_reference	additional.fields	Additional metadata fields not covered by the UDM schema.
deviceDescr, desc	metadata.description	Description of the event.
has_principal, has_target	metadata.event_type	Type of event (e.g., USER_LOGIN, NETWORK_CONNECTION).
eventType	metadata.product_event_type	Product-specific event type.
protocol	network.ip_protocol	IP protocol used in the network connection.
principal	principal	The principal entity involved in the event.
deviceType	principal.asset.category	Category of the asset.
modelNameNo, manufacturer, mfgName	principal.asset.hardware	Hardware information for the asset.
fqdn, deviceName	principal.asset.hostname	Hostname of the asset.
ipAddress, srcIp	principal.asset.ip	IP address of the asset.
fqdn, deviceName	principal.hostname	Hostname associated with the principal.
ipAddress, srcIp	principal.ip	IP address associated with the principal.
srcHost, srcMac, deviceId, equipMac, clientId	principal.mac	MAC address associated with the principal.
osType	principal.platform	Operating system platform.
osVersion	principal.platform_version	Version of the operating system platform.
srcPort	principal.port	Port number associated with the principal.
groupList, deviceGroup	principal.user.group_identifiers	List of group identifiers for the user.
alarmType, alarmCategory, riskState, level, severityLevel	security_result	Security result information.
dstHost	target.asset.hostname	Hostname of the target asset.
dstIp, ip	target.asset.ip	IP address of the target asset.
dstHost	target.hostname	Hostname of the target.
dstIp, ip	target.ip	IP address of the target.
dstPort	target.port	Port number of the target.
	metadata.vendor_name	Vendor/company name.
	metadata.product_name	Product name.
timestamp	metadata.event_timestamp	Mapped from changelog

Change Log

View the Change Log for this parser

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