Configuring Trend Micro Vision One Connectors

The Trend Micro Vision One connector allows you to collect alert details and observed attack techniques from your Trend Micro deployment, and add that to the Stellar Cyber data lake for analysis and threat hunting.

This topic refers to configuring a Trend Micro Vision One connector. Also see: 

• Configuring Trend Micro Apex Central Connectors
• Configuring Trend Micro Cloud One Connectors

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: Trend Micro Vision One

Adding a Trend Micro Vision One Connector

To add a Trend Micro Vision One connector:

1. Obtain Authentication details for integration
2. Add the connector in Stellar Cyber
3. Test the connector
4. Use the connector

Use our example as a guideline, as you might be using a different software version.

Obtaining Authentication Details for Stellar Cyber Integration

Before you add a Trend Micro Connector, you must obtain information that allows the Stellar Cyber connector to authenticate correctly.

1. Log in to the Trend Micro Apex Central console as the user who will be associated with the Stellar Cyber app (http://manage.trendmicro.com).

2. When the console has loaded, select the menu bar for Vision One. If prompted as below, accept the option to proceed to the next screen.

   

3. The Vision One Console displays. Navigate to XDR | Managed XDR and ensure it is Enabled.

4. Navigate to Administration tab and access User Accounts.

5. Open the user account that will be associated with your Stellar Cyber connector. Make note of the Authentication token.

   

6. Click Close.

7. Note the API URL from the location that corresponds to your environment.

   Region	FQDN
   Australia	api.au.xdr.trendmicro.com
   European Union	api.eu.xdr.trendmicro.com
   India	api.in.xdr.trendmicro.com
   Japan	api.xdr.trendmicro.co.jp
   Singapore	api.sg.xdr.trendmicro.com
   United States	api.xdr.trendmicro.com

Adding the Connector in Stellar Cyber

After you have noted the authentication information from the Trend Micro app integration, you can add the Trend Micro Vision One connector in Stellar Cyber:

1. Log in to Stellar Cyber.

2. Click System | Connectors (under Integrations). The Connector Overview appears.

   

3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

   

   The asterisk (*) indicates a required field.

4. Choose Endpoint Security from the Category drop-down.

5. Choose Trend Micro Vision One from the Type drop-down.

6. For this connector, the supported Function is Respond, which is enabled already.

7. Enter a Name.

   Notes:

   • This field does not accept multibyte characters.
   • It is recommended that you follow a naming convention such as tenantname-connectortype.

8. Choose a Tenant Name for the tenants who will have access to this connector.

9. Choose the device on which to run the connector.

   • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

   • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

10. (Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.

11. Click Next. The Configuration tab appears.

    

    The asterisk (*) indicates a required field.

12. Enter the API base URL. Use the table noted in the previous section to add the appropriate URL for your region.

    For release versions prior to v4.3.4, ensure the URL does not include a trailing "/" symbol.

13. Enter the Bearer token value. This is the authentication token you copied in the section above.

14. Choose the Interval (min). This is how often the logs are collected.

15. Choose the Content Type you would like to collect. The logs for Alerts and Observed Attack Techniques are supported.

16. Click Next. The final confirmation tab appears.

    

17. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

18. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

    • This prompt only occurs during the initial create connector process when Collect is enabled.

    • Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.

    • The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.

    The Connector Overview appears.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates authentication and connectivity).

1. Click System | Connectors (under Integrations). The Connector Overview appears.

   

2. Locate the connector by name that you added, or modified, or that you want to test.

3. Click Test at the right side of that row. The test runs immediately.

   Note that you may run only one test at a time.

Using the Connector to Investigate

When an event has occurred on a host known to the Trend Micro connector, you can use this connector to investigate further.

1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
2. Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.