Collect Trend Micro Apex One logs

Supported in:

Google secops SIEM

This document explains how to ingest Trend Micro Apex One logs to Google Security Operations using the Bindplane agent.

Trend Micro Apex One is an endpoint security platform that generates CEF-formatted syslog messages for malware detections, intrusion prevention events, suspicious file activity, web reputation verdicts, and device control events. The parser extracts fields from CEF-formatted logs 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 Trend Micro Apex Central server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Administrator access to the Apex Central console

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" /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)" 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 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/trendmicro_apex_one:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: TRENDMICRO_APEX_ONE
        raw_log_field: body

service:
    pipelines:
        logs/trendmicro_apex_one_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/trendmicro_apex_one

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.
  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 syslog forwarding in Trend Micro Apex One

Sign in to the Apex Central console using administrator credentials.
Go to Administration > Settings > Syslog Settings.
Check the box labeled Enable syslog forwarding.
Configure Syslog Server Details:
- Server Address: Enter the Bindplane agent IP address or FQDN.
- Port: Enter the Bindplane agent port number (for example, 514 for UDP).
- Protocol: Select UDP as the transmission protocol.
Optional: Configure Proxy Settings — Check Use a SOCKS proxy server (ensure proxy settings are configured under Administration > Settings > Proxy Settings).
Log Format: Select CEF.
Frequency: Define how often logs are forwarded to the Syslog server.
Log Type: Select Security logs and Product information.
Click Test Connection to ensure Apex Central can communicate with the Syslog server.
Click Save to apply the settings.

UDM mapping table

Log Field	UDM Mapping	Logic
`act`	`security_result.action_details`	Directly mapped from the `act` field.
`ApexCentralHost`	`about.asset.asset_id`	Used as part of the asset_id generation logic. The value "Trend Micro.Apex Central:" is prepended to the `deviceExternalId` field.
`app`	`target.port`	Directly mapped from the `app` field.
`cat`	`security_result.category_details`	Directly mapped from the `cat` field.
`cn1`	`additional.fields[4].value.string_value`	Directly mapped from the `cn1` field. Key is derived from `cn1Label`.
`cn1Label`	`additional.fields[4].key`	Directly mapped from the `cn1Label` field.
`cn2`	`additional.fields[6].value.string_value`	Directly mapped from the `cn2` field. Key is derived from `cn2Label`.
`cn2Label`	`additional.fields[6].key`	Directly mapped from the `cn2Label` field.
`cn3`	`additional.fields[2].value.string_value`	Directly mapped from the `cn3` field. Key is derived from `cn3Label`.
`cn3Label`	`additional.fields[2].key`	Directly mapped from the `cn3Label` field.
`cs1`	`additional.fields[0].value.string_value`	Directly mapped from the `cs1` field. Key is derived from `cs1Label`.
`cs1Label`	`additional.fields[0].key`	Directly mapped from the `cs1Label` field.
`cs2`	`additional.fields[1].value.string_value`	Directly mapped from the `cs2` field. Key is derived from `cs2Label`.
`cs2Label`	`additional.fields[1].key`	Directly mapped from the `cs2Label` field.
`cs3`	`additional.fields[5].value.string_value`	Directly mapped from the `cs3` field. Key is derived from `cs3Label`.
`cs3Label`	`additional.fields[5].key`	Directly mapped from the `cs3Label` field.
`cs4`	`additional.fields[0].value.string_value`	Directly mapped from the `cs4` field. Key is derived from `cs4Label`.
`cs4Label`	`additional.fields[0].key`	Directly mapped from the `cs4Label` field.
`cs5`	`additional.fields[2].value.string_value`	Directly mapped from the `cs5` field. Key is derived from `cs5Label`.
`cs5Label`	`additional.fields[2].key`	Directly mapped from the `cs5Label` field.
`cs6`	`additional.fields[7].value.string_value`	Directly mapped from the `cs6` field. Key is derived from `cs6Label`.
`cs6Label`	`additional.fields[7].key`	Directly mapped from the `cs6Label` field.
`deviceExternalId`	`about.asset.asset_id`	Used as part of the asset_id generation logic. The value "Trend Micro.Apex Central:" is prepended to this field.
`deviceNtDomain`	`about.administrative_domain`	Directly mapped from the `deviceNtDomain` field.
`devicePayloadId`	`additional.fields[3].value.string_value`	Directly mapped from the `devicePayloadId` field. Key is hardcoded as "devicePayloadId".
`deviceProcessName`	`about.process.command_line`	Directly mapped from the `deviceProcessName` field.
`dhost`	`target.hostname`	Directly mapped from the `dhost` field.
`dntdom`	`target.administrative_domain`	Directly mapped from the `dntdom` field.
`dst`	`target.ip`	Directly mapped from the `dst` field.
`duser`	`target.user.userid`, `target.user.user_display_name`	Directly mapped from the `duser` field.
`dvchost`	`about.hostname`	Directly mapped from the `dvchost` field.
`fileHash`	`about.file.full_path`	Directly mapped from the `fileHash` field.
`fname`	`additional.fields[9].value.string_value`	Directly mapped from the `fname` field. Key is hardcoded as "fname".
`message`	`metadata.product_event_type`	The CEF header is extracted from the message field.
`request`	`target.url`	Directly mapped from the `request` field.
`rt`	`metadata.event_timestamp`	Directly mapped from the `rt` field.
`shost`	`principal.hostname`	Directly mapped from the `shost` field.
`src`	`principal.ip`	Directly mapped from the `src` field.
`TMCMdevicePlatform`	`principal.platform`	Mapped based on logic in the parser. Values are normalized to "WINDOWS", "MAC", or "LINUX".
`TMCMLogDetectedHost`	`principal.hostname`	Directly mapped from the `TMCMLogDetectedHost` field.
`TMCMLogDetectedIP`	`principal.ip`	Directly mapped from the `TMCMLogDetectedIP` field. Derived from parser logic based on the presence of other fields. Possible values are "USER_UNCATEGORIZED", "STATUS_UPDATE", or "GENERIC_EVENT". Hardcoded to "TRENDMICRO_APEX_ONE". Hardcoded to "TRENDMICRO_APEX_ONE". Extracted from the CEF header in the `message` field. Hardcoded to "LOW".

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