↳ GitHub sourceConnector
[Deprecated] Trend Micro Apex One via Legacy Agent
Description
The [Trend Micro Apex One](https://www.trendmicro.com/en_us/business/products/user-protection/sps/endpoint.html) data connector provides the capability to ingest [Trend Micro Apex One events](https://aka.ms/sentinel-TrendMicroApex-OneEvents) into Microsoft Sentinel. Refer to [Trend Micro Apex Central](https://aka.ms/sentinel-TrendMicroApex-OneCentral) for more information.
- Declared status
- 1
- Declared author / publisher
- Trend Micro
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
>This data connector depends on a parser based on a Kusto Function to work as expected [**TMApexOneEvent**](https://aka.ms/sentinel-TMApexOneEvent-parser) which is deployed with the Microsoft Sentinel Solution.
>**NOTE:** This data connector has been developed using Trend Micro Apex Central 2019
1. Linux Syslog agent configuration
Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.
> Notice that the data from all regions will be stored in the selected workspace
1.1 Select or create a Linux machine
Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-prem environment, Azure or other clouds.
1.2 Install the CEF collector on the Linux machine
Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP.
> 1. Make sure that you have Python on your machine using the following command: python -version.
> 2. You must have elevated permissions (sudo) on your machine.
Run the following command to install and apply the CEF collector:
2. Forward Common Event Format (CEF) logs to Syslog agent
[Follow these steps](https://docs.trendmicro.com/en-us/enterprise/trend-micro-apex-central-2019-online-help/detections/logs_001/syslog-forwarding.aspx) to configure Apex Central sending alerts via syslog. While configuring, on step 6, select the log format **CEF**.
3. Validate connection
Follow the instructions to validate your connectivity:
Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.
>It may take about 20 minutes until the connection streams data to your workspace.
If the logs are not received, run the following connectivity validation script:
> 1. Make sure that you have Python on your machine using the following command: python -version
>2. You must have elevated permissions (sudo) on your machine
Run the following command to validate your connectivity:
4. Secure your machine
Make sure to configure the machine's security according to your organization's security policy
[Learn more >](https://aka.ms/SecureCEF)
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
9800e51↗- Source identifier
TrendMicroApexOne
Additional source files 1
Solutions/Trend Micro Apex One/Data Connectors/TrendMicro_ApexOne.jsonsource ↗GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC