Configuring Trend Micro Cloud One Workload Security Connectors

This connector allows you to discover Trend Micro Cloud One Workload Security managed computer assets, and add them to the Stellar Cyber data lake for analysis and threat hunting.

This topic refers to configuring a Trend Micro Cloud One Workload Security connector. Also see: 

• Configuring Trend Micro Apex Central Connectors
• Configuring Trend Micro Vision 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 Cloud One

Adding a Trend Micro Cloud One Connector

To add a Trend Micro Cloud One Workload Security connector:

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

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 Cloud One console as the user who will be associated with the Stellar Cyber app (http://cloudone.trendmicro.com).

2. When the console has loaded, access the Workload Security screen: 

   

3. Navigate to Administration > User Management > API.

   

4. Click Add. In the displayed dialog, add the following:

   • Name: This is the name you will use to identify the app as being associated with Stellar Cyber

   • Role: Select Full Access.

   

5. Click Next.

6. The dialog updates to display the secret key for your new app. Make note of this for use when you configure your connector. You cannot retrieve this key after you close the dialog, so make note of it now. If you accidentally lose the information, you must create a new app.

   

7. Click Close.

   The API Keys screen appears and shows the newly added application in the table.

Adding the Connector in Stellar Cyber

After you have noted the authentication information from the Trend Micro app integration steps, you can add the Trend Micro Cloud One Workload Security 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 Cloud One Workload Security from the drop-down.

6. For this connector, the supported Function is Collect, 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 URL. This is the API URL associated with the API key. Trend Micro legacy format is https://cloudone.trendmicro.com/api , but migrated to a regional format as follows: https://workload.{region}.cloudone.trendmicro.com/api (example: https://workload.us-1.cloudone.trendmicro.com/api/).

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

13. Enter the API Key. This is the Secret Key associated with the application you created above in the Trend Micro Cloud One Workload Security console.

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 Computers are supported.

    Stellar Cyber gets the computer object, normalizes some of the fields, creates an asset record, and populates Syslog. The fields in Syslog are trendmicro_cloudone.<fieldname>, which may include any of the fields for Computers as follows: https://cloudone.trendmicro.com/docs/workload-security/api-reference/tag/Computers

    In addition, the computers are sent to the Investigate | Asset Analytics page.

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.

Verifying Ingestion

To verify ingestion:

1. Click Investigate | Threat Hunting. The Interflow Search tab appears.

2. Change the Indices for the type of content you collected:

   • For Computers only, change the Indices to Syslog.

   • For Computers only, change the Indices to Assets.

   The table immediately updates to show ingested Interflow records.