# Collect Trend Micro Email Security logs

Supported in:

This document explains how to ingest Trend Micro Email Security logs to Google Security Operations using Bindplane. Trend Micro Email Security is a cloud-based email gateway that protects organizations against spam, malware, phishing, ransomware, and advanced targeted attacks before they reach users' mailboxes. It provides URL filtering, attachment sandboxing, and data loss prevention for inbound and outbound email traffic.

## Before you begin

Make sure you have the following prerequisites:

- A Google SecOps instance.
- A Windows 2016 or later or Linux host with systemd.
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
- Privileged access to the Trend Micro Email Security administration console.

## 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](https://console.cloud.google.com/) 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]
> **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 **Settings \> Data Management \> Collection Agents** . If you are on a SIEM-only platform, go to **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]
> **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 **Settings \> Administration \> Profile** . If you are on a SIEM-only platform, go to **Settings \> Profile**.
3. Copy and save the **Customer ID** from the **Organization Details** section.

## Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

### Windows installation

1. Open the **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](https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi)" /quiet

### 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](https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh))" install_unix.sh

### Additional installation resources

For additional installation options, consult this [installation guide](https://docs.cloud.google.com/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).

> [!NOTE]
> **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 Bindplane agent to ingest syslog and send to Google SecOps

1. Access the configuration file:

   - Locate the `config.yaml` file. Typically, it's in the `/opt/observiq-otel-collector/` directory on Linux or in the installation directory on Windows.
   - Open the file using a text editor (for example, `nano`, `vi`, or Notepad).
2. Edit the `config.yaml` file as follows:

       receivers:
         tcplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:514"

       exporters:
         chronicle/chronicle_w_labels:
           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
           # Adjust the path to the credentials file you downloaded in Step 1
           creds_file_path: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: YOUR_CUSTOMER_ID
           endpoint: chronicle.googleapis.com
           # Add optional ingestion labels for better organization
           log_type: 'TRENDMICRO_EMAIL_SECURITY'
           raw_log_field: body
           ingestion_labels:

       service:
         pipelines:
           logs/source0__chronicle_w_labels-0:
             receivers:
               - tcplog
             exporters:
               - chronicle/chronicle_w_labels

- Replace the port and IP address as required in your infrastructure.
- 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.
- Replace `<PROJECT_NUMBER>` with the project number from **IAM \& Admin \> Settings**.
- Replace `YOUR_CUSTOMER_ID` with the actual Customer ID.
- Update `/path/to/ingestion-authentication-file.json` to the file path where the service account key file (Option 1) was saved in Step 1.

### 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](https://docs.cloud.google.com/chronicle/docs/reference/ingestion-api#regional-endpoints) (for example, `europe-malachiteingestion-pa.googleapis.com`).

      exporters:
        chronicle/chronicle_w_labels:
          compression: gzip
          # Adjust the path to the credentials file you downloaded in Step 1
          creds_file_path: '/path/to/ingestion-authentication-file.json'
          # Replace with your actual customer ID from Step 2
          customer_id: YOUR_CUSTOMER_ID
          endpoint: malachiteingestion-pa.googleapis.com
          # Add optional ingestion labels for better organization
          log_type: 'TRENDMICRO_EMAIL_SECURITY'
          raw_log_field: body
          ingestion_labels:

> [!NOTE]
> **Note:** This exporter will stop working when the Ingestion API is discontinued on July 20, 2027.

## Restart the Bindplane agent to apply the changes

1. To restart the Bindplane agent in **Linux**, run the following command:

       sudo systemctl restart observiq-otel-collector

2. To restart the Bindplane agent in Windows, you can either use the **Services** console or enter the following command:

       net stop observiq-otel-collector && net start observiq-otel-collector

## Configure Trend Micro Email Security syslog forwarding

To configure Trend Micro Email Security to forward logs to the Bindplane agent via syslog, follow these steps:

1. Sign in to the **Trend Micro Email Security** administration console.
2. Go to **Administration \> Syslog Settings**.
3. Click **Add** to create a new syslog server profile.

4. Provide the following configuration details:

   - **Server Address** : Enter the IP address of the Bindplane agent host (for example, `192.168.1.100`).
   - **Port** : Enter `514` (or the port configured in the Bindplane agent).
   - **Protocol** : Select **TCP**.
   - **Format** : Select **CEF** (Common Event Format).
5. In the **Log Types** section, select the log categories to forward:

   - **Policy Events** - email filtering policy actions.
   - **Spam Detection** - spam and graymail events.
   - **Malware Detection** - virus and malware detection events.
   - **Ransomware Detection** - ransomware detection events.
   - **URL Analysis** - URL clicking and Time-of-Click protection events.
   - **Advanced Threat Protection** - sandbox analysis events.
   - **Data Loss Prevention** - DLP policy violation events.
   - **Content Filtering** - content filter rule events.
6. Click **Save**.

7. Click **Test Connection** to verify that logs are being sent to the Bindplane agent.

8. Verify logs are arriving by checking the Bindplane agent logs.

For more information, see the [Trend Micro Email Security documentation](https://docs.trendmicro.com/en-us/documentation/article/trend-micro-email-security-online-help).

## UDM mapping table

| Log Field | UDM Mapping | Logic |
|---|---|---|
| `additional_cn1` | `additional.fields` | Merged |
| `additional_cs1` | `additional.fields` | Merged |
| `additional_cs2` | `additional.fields` | Merged |
| `additional_cs3` | `additional.fields` | Merged |
| `additional_cs4` | `additional.fields` | Merged |
| `additional_cs5` | `additional.fields` | Merged |
| `additional_cs6` | `additional.fields` | Merged |
| `message` | `extensions.auth.type` | Mapped: `login` → `AUTHTYPE_UNSPECIFIED` |
| `msg` | `metadata.description` | Directly mapped |
| `rt` | `metadata.event_timestamp` | Parsed as `ISO8601` |
| `cs1` | `metadata.event_type` | Mapped: `phishing` → `SCAN_UNCATEGORIZED` |
| `message` | `metadata.event_type` | Mapped: `CEF:0` → `GENERIC_EVENT`, `login` → `USER_LOGIN` |
| `cs1` | `metadata.product_event_type` | Directly mapped |
| `network_direction` | `network.direction` | Mapped: `INCOMING` → `INBOUND`, `OUTGOING` → `OUTBOUND` |
| `cs2` | `principal.hostname` | Directly mapped |
| `principal_ip` | `principal.hostname` | Directly mapped |
| `principal_ip` | `principal.ip` | Merged |
| `message` | `principal.user.userid` | Mapped: `login` → `target.user.userid` |
| `suser` | `principal.user.userid` | Directly mapped |
| `act` | `security_result.action` | Mapped: `ALLOW` → `act`, `DENY` → `security_result_action`, `QUARANTINE` → `act` |
| `security_result_action` | `security_result.action` | Merged |
| `act` | `security_result.action_details` | Directly mapped |
| `cs5` | `security_result.rule_name` | Directly mapped |
| `severity` | `security_result.severity` | Mapped: `"0", "1", "2", "3", "LOW"` → `LOW`, \`"4", "5", "6", "MEDIUM", "SUBSTANTIAL", "INFO"... |
| `cs6` | `target.url` | Directly mapped |
| `duser` | `target.user.email_addresses` | Mapped: `;` → `emailId` |
| `emailId` | `target.user.email_addresses` | Merged |
| `duser` | `target.user.userid` | Directly mapped |
| `principal.user.userid` | `target.user.userid` | Renamed/mapped |
| N/A | `extensions.auth.type` | Constant: `AUTHTYPE_UNSPECIFIED` |
| N/A | `metadata.event_type` | Constant: `GENERIC_EVENT` |
| N/A | `network.direction` | Constant: `INBOUND` |
| N/A | `principal.user.userid` | Constant: `target.user.userid` |
| N/A | `security_result.severity` | Constant: `LOW` |

## Change Log

[View the Change Log for this parser](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/trendmicro-email-security-changelog)

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)