|
| 1 | +--- |
| 2 | +id: trend-micro-source |
| 3 | +title: Trend Micro Source |
| 4 | +sidebar_label: Trend Micro |
| 5 | +tags: |
| 6 | + - cloud-to-cloud |
| 7 | + - trend-micro |
| 8 | +description: Learn how to collect alert details from Trend Micro platform. |
| 9 | +--- |
| 10 | +import CodeBlock from '@theme/CodeBlock'; |
| 11 | +import ExampleJSON from '/files/c2c/trend-micro/example.json'; |
| 12 | +import MyComponentSource from '!!raw-loader!/files/c2c/trend-micro/example.json'; |
| 13 | +import TerraformExample from '!!raw-loader!/files/c2c/trend-micro/example.tf'; |
| 14 | +import useBaseUrl from '@docusaurus/useBaseUrl'; |
| 15 | + |
| 16 | +<img src={useBaseUrl('img/send-data/trend-micro-logo.png')} alt="webex-logo" width="120" /> |
| 17 | + |
| 18 | +Trend Micro is a global leader in cybersecurity solutions, offering a range of products and services to protect against online threats. The company specializes in security for cloud environments, networks, endpoints, and hybrid infrastructure, leveraging advanced threat intelligence and artificial intelligence. |
| 19 | + |
| 20 | +## Data collected |
| 21 | + |
| 22 | +| Polling Interval | Data | |
| 23 | +| :--- | :--- | |
| 24 | +| 15 min | [Alert Details](https://automation.trendmicro.com/xdr/api-v3/#tag/Workbench/paths/~1v3.0~1workbench~1alerts/get) | |
| 25 | + |
| 26 | +## Setup |
| 27 | + |
| 28 | +### Vendor configuration |
| 29 | + |
| 30 | +:::note |
| 31 | +Ensure that you have view, filter, and search permissions for the alert endpoint. |
| 32 | +::: |
| 33 | + |
| 34 | +The Trend Micro source requires you to provide a API Base URL and Authentication Token. To obtain these, follow the steps below. |
| 35 | + |
| 36 | +- **Base URL**. The integration requires the configuration of the Trend Micro Vision One domain. Trend Micro Vision One API Regions are: |
| 37 | + | Region | Base URL | |
| 38 | + |:--|:--| |
| 39 | + | Australia | `api.au.xdr.trendmicro.com` | |
| 40 | + | European Union | `api.eu.xdr.trendmicro.com` | |
| 41 | + | India | `api.in.xdr.trendmicro.com` | |
| 42 | + | Japan | `api.xdr.trendmicro.co.jp` | |
| 43 | + | Singapore | `api.sg.xdr.trendmicro.com` | |
| 44 | + | United Arab Emirates | `api.mea.xdr.trendmicro.com` | |
| 45 | + | United States | `api.xdr.trendmicro.com` | |
| 46 | + | United States (for Government) | `api.usgov.xdr.trendmicro.com` | |
| 47 | +- **Bearer token**. To generate the authentication token, refer to the [Trend Micro Documentation](https://docs.trendmicro.com/en-us/documentation/article/cloud-app-security-integration-api-online-help-generating-an-authen). |
| 48 | + |
| 49 | +### Source configuration |
| 50 | + |
| 51 | +When you create an Trend Micro source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see [Configure a Hosted Collector](/docs/send-data/hosted-collectors/configure-hosted-collector). |
| 52 | + |
| 53 | +To configure an Trend Micro source: |
| 54 | +1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. |
| 55 | +1. On the Collection page, click **Add Source** next to a Hosted Collector. |
| 56 | +1. Search for and select **Trend Micro**. |
| 57 | +1. Enter a **Name** for the Source. The description is optional. |
| 58 | +1. (Optional) For **Source Category**, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called `_sourceCategory`. |
| 59 | +1. (Optional) **Fields**. Click the **+Add** button to define the fields you want to associate. Each field needs a name (key) and value. |
| 60 | + *  A green circle with a check mark is shown when the field exists in the Fields table schema. |
| 61 | + *  An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped. |
| 62 | +1. **API Base URL**. Enter the [Base URL](#vendor-configuration) to fetch the data from the Trend Micro Vision One source. |
| 63 | +1. **Auth Token**. Enter the authentication token collected from the [Trend Micro platform](#vendor-configuration). |
| 64 | +1. **Polling Interval**. The polling interval is set for 15 minutes by default. You can adjust it based on your needs. This sets how often the Source checks for new data. |
| 65 | +1. **Processing Rules for Logs**. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in [Create a Processing Rule](/docs/send-data/collection/processing-rules/create-processing-rule). |
| 66 | +1. When you are finished configuring the Source, click **Save**. |
| 67 | + |
| 68 | +## JSON schema |
| 69 | + |
| 70 | +Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See [SON to configure Sources](/docs/send-data/use-json-configure-sources) for details. |
| 71 | + |
| 72 | +| Parameter | Type | Value | Required | Description | |
| 73 | +|:--|:--|:--|:--|:--| |
| 74 | +| schemaRef | JSON Object | `{"type":"Trend Micro"}` | Yes | Define the specific schema type. | |
| 75 | +| sourceType | String | `"Universal"` | Yes | Type of source. | |
| 76 | +| config | JSON Object | [Configuration object](#configuration-object) | Yes | Source type specific values. | |
| 77 | + |
| 78 | +### Configuration Object |
| 79 | + |
| 80 | +| Parameter | Type | Required | Default | Description | Example | |
| 81 | +|:--|:--|:--|:--|:--|:--| |
| 82 | +| name | String | Yes | `null` | Type a desired name of the source. The name must be unique per Collector. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_source`. | `"mySource"` | |
| 83 | +| description | String | No | `null` | Type a description of the source. | `"Testing source"` |
| 84 | +| category | String | No | `null` | Type a category of the source. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_sourceCategory`. See [best practices](/docs/send-data/best-practices) for details. | `"mySource/test"` |
| 85 | +| fields | JSON Object | No | `null` | JSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.|`{"_siemForward": false, "fieldA": "valueA"}` | |
| 86 | +| apiBaseUrl | String | Yes | `null` | The base URL to fetch the data from the Trend Micro Vision One source. | | |
| 87 | +| authToken | String | Yes | `null` | Client Authentication Token to be used in the API header. | | |
| 88 | +| pollingInterval | integer | Yes | `15 minutes` | Time interval (in minutes) after which the source will check for new data. | | |
| 89 | + |
| 90 | +### JSON example |
| 91 | + |
| 92 | +<CodeBlock language="json">{MyComponentSource}</CodeBlock> |
| 93 | + |
| 94 | +<a href="/files/c2c/trend-micro/example.json" target="_blank">Download example</a> |
| 95 | + |
| 96 | +### Terraform example |
| 97 | + |
| 98 | +<CodeBlock language="json">{TerraformExample}</CodeBlock> |
| 99 | + |
| 100 | +<a href="/files/c2c/trend-micro/example.tf" target="_blank">Download example</a> |
| 101 | + |
| 102 | +## FAQ |
| 103 | + |
| 104 | +:::info |
| 105 | +Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources. |
| 106 | +::: |
0 commit comments