av.trendmicro
Introduction
The tags beginning with av.trendmicro identify events generated by Trend Micro.Â
Valid tags and data tables
The full tag must have 5 levels. The first two are fixed as av.trendmicro The third level identifies the type of events sent, and the fourth level indicates the event subtype.Â
Technology | Brand | Type | Subtype 1 | Subtype 2 |
---|---|---|---|---|
av | trendmicro |
|
|
|
|
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
---|---|
av.trendmicro.deepsec.agent.cef | av.trendmicro.deepsec.agent |
av.trendmicro.deepsec.agent.leef | av.trendmicro.deepsec.agent |
av.trendmicro.deepsec.manager.cef | av.trendmicro.deepsec.manager |
av.trendmicro.deepsec.manager.leef | av.trendmicro.deepsec.manager |
How is the data sent to Devo?
Logs generated by Trend Micro must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rules below:
You will need to set up a rule on the relay to correctly process and forward the events received from Trend Micro. In the example below, Â you should use any port that you can dedicate to these events.
Trend Micro Deep Security (Agent|Manager)
Rules | Relay screenshot |
---|---|
LEEF Format
|
Trend Micro Deep Security (Agent|Manager)
Rules | Relay screenshot |
---|---|
CEF Format
| Â |
Â