Collect Trend Micro Apex Central logs

Supported in:

Google secops SIEM

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

Trend Micro Apex Central is a centralized security management console for Trend Micro products that provides threat detection, policy management, and security event logs across endpoints, servers, and network layers. It outputs logs in CEF format via syslog.

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
Privileged access to Trend Micro Apex Central with administrator permissions

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

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

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 Trend Micro Apex Central syslog forwarding

Sign in to the Apex Centralmanagement console.
Go to Administration > Settings > Syslog Settings.
Enable syslog forwarding by selecting the Enable Syslog Forwardingcheckbox.
Provide the following configuration details:
- Server address: Enter the IP address of the Bindplane agent host.
- Port: Enter 514 .
- Protocol: Select TCP.
- Format: Select CEF(Common Event Format).
Select the log types to forward:
- Detection logs
- Policy violation events
- Security events
- System events
Click Saveto apply the configuration.
Verify that logs are being sent by checking the Bindplane agent logs.

UDM mapping table

Log Field	UDM Mapping	Logic
var_eventFormatVersion, var_severity, dntdom_label, additional_cs6, additional_product_version, additional_cat, additional_msg, additional_dvchost, var_cs1_label, var_cs1, var_cs2, var_cs5, var_deviceExternalId, var_c6a3, var_cn1_label, var_cn1, var_cn2, var_cs4_label, var_cs4, var_c6a2, var_cn3, var_cnt, var_TMCMLogTarget, var_deviceDirection	additional.fields	Additional vendor-specific event data
rt	metadata.event_timestamp	Timestamp when the event occurred
event_name	metadata.event_type	Type of event (e.g., USER_LOGIN, NETWORK_CONNECTION)
event_id	metadata.product_event_type	Type of event from the product
devicePayloadId	metadata.product_log_id	Unique identifier for the log entry from the product
cs3, product_version	metadata.product_version	Version of the product
vendor	metadata.vendor_name	Vendor/company name
product_name	metadata.product_name	Product name
app	network.application_protocol	Application protocol
deviceDirection	network.direction	Direction of the network traffic
proto	network.ip_protocol	IP protocol
domain, dntdom	principal.administrative_domain	Administrative domain of the principal
dhost	principal.asset.hostname	Hostname of the asset
TMCMLogDetectedIP, princ_ip	principal.asset.ip	IP address of the asset
platform	principal.asset.platform	Platform of the asset
patch_level	principal.asset.platform_patch_level	Patch level of the platform
version	principal.asset.platform_version	Version of the platform
dvchost, dhost	principal.hostname	Source hostname
TMCMLogDetectedIP, princ_ip	principal.ip	IP address of the principal
smac	principal.mac	MAC address of the principal
spt	principal.port	Port of the principal
deviceProcessName	principal.process.file.full_path	Full path of the process file
duser	principal.user.userid	User ID of the principal
security_result	security_result	Security result
act	security_result.action	Action taken by the security product
act, cs5	security_result.action_details	Details of the action taken
cs4	security_result.category_details	Details about the category
cs1, cn2	security_result.description	Description of the security result
var_cn2_label	security_result.detection_fields	Fields related to detection
cn1	security_result.rule_id	ID of the rule
cs1	security_result.rule_name	Name of the rule
cn3, severity, cn4, cn2	security_result.severity	Severity of the security result
event_name	security_result.threat_name	Name of the threat
cnt	security_result.verdict_info	Information about the verdict
shost	src.hostname	Source hostname
src, host_ip	src.ip	Source IP address
suser	src.user.userid	User ID of the source
deviceNtDomain	target.administrative_domain	Administrative domain of the target
c6a3	target.asset.ip	IP address of the asset
filePath, sproc	target.file.full_path	Full path of the file
fname	target.file.names	Names of the file
fileHash	target.file.sha1	SHA1 hash of the file
c6a3	target.ip	IP address of the target
dmac	target.mac	MAC address of the target
dpt	target.port	Port of the target
cs3, sproc	target.process.file.full_path	Full path of the process file
request	target.url	URL of the target
duser	target.user.userid	User ID of the target

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