Trend Micro
Visualize Trend Micro administrators, endpoint agents, and devices, map Trend Micro agents to devices and owners, and monitor changes through queries and alerts.
- Installation guide
- Trend Micro data model
Installation
For this integration, you will need to create an API key on Trend Micro for use within JupiterOne.
See Trend Micro's documentation for more information on creating and managing API keys.
Configuration in JupiterOne
To install the Trend Micro integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Trend Micro. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Trend Micro account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Your Trend Micro API Key generated for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
API Key | trend_micro_api_key | Key |
Administrator | trend_micro_administrator | User |
Administrator Role | trend_micro_administrator_role | AccessRole |
File Storage AWS Stack | trend_cloud_one_file_storage_aws_stack | Configuration |
File Storage Azure Stack | trend_cloud_one_file_storage_azure_stack | Configuration |
File Storage GCP Stack | trend_cloud_one_file_storage_gcp_stack | Configuration |
File Storage Scan Event Finding | trend_cloud_one_file_storage_finding | Finding |
Workload Computer Group | trend_cloud_one_workload_computer_group | Group |
Workload Sensor | trend_cloud_one_workload_sensor | HostAgent |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
trend_cloud_one_file_storage_aws_stack | MANAGES | trend_cloud_one_file_storage_aws_stack |
trend_cloud_one_file_storage_aws_stack | IDENTIFIED | trend_cloud_one_file_storage_finding |
trend_cloud_one_file_storage_azure_stack | MANAGES | trend_cloud_one_file_storage_azure_stack |
trend_cloud_one_file_storage_azure_stack | IDENTIFIED | trend_cloud_one_file_storage_finding |
trend_cloud_one_file_storage_gcp_stack | IDENTIFIED | trend_cloud_one_file_storage_finding |
trend_cloud_one_file_storage_gcp_stack | MANAGES | trend_cloud_one_file_storage_gcp_stack |
trend_cloud_one_workload_computer_group | HAS | trend_cloud_one_workload_sensor |
trend_micro_administrator | ASSIGNED | trend_micro_administrator_role |