Loading

Trend Micro Vision One Integration for Elastic

Version 2.8.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.1.4
9.0.7
8.19.4

The Trend Micro Vision One integration allows you to monitor Alert, Audit, Detection, Endpoint activity, Network activity, and Telemetry activity. Trend Micro Vision One refers to the ability to do detection and response across email, endpoints, servers, cloud workloads, and networks using a single Trend Micro Vision One platform or the managed Trend Micro Vision One service.

This module has been tested against Trend Micro Vision One API version 3.0.

This integration periodically queries the Trend Micro Vision One REST API to retrieve Alert, Audit, Detection, Endpoint activity, Network activity, and Telemetry logs.

This integration collects log messages of the following types:

  • Alert: Displays information about workbench alerts. Refer to more details in the doc here.
  • Audit: Displays log entries that match the specified search criteria. Refer to more details in the doc here.
  • Detection: Displays search results from the Detection Data source. Refer to more details in the doc here.
  • Endpoint activity: Displays search results from the Endpoint activity Data source. Refer to more details in the doc here.
  • Network activity: Displays search results from the Network activity Data source. Refer to more details in the doc here.
  • Telemetry: Displays telemetry events from the Datalake Pipeline API. Refer to more details in the doc here.

Integrating Trend Micro Vision One alert, audit, detection, endpoint activity, network activity, and telemetry events with Elastic SIEM provides centralized visibility into security events and operations.

  1. Log on to the Trend Micro Vision One console.

  2. On the Trend Vision One console, go to Administration -> API Keys.

  3. Generate a new API Key. Click Add API key. Specify the settings of the new API key.

    • Name: A meaningful name that can help you identify the API key.

    • Role: The user role assigned to the key. API keys can use either predefined or custom user roles. Custom roles can be created by navigating to Administration -> User Roles -> Add Role. The role must have appropriate API access permission to fetch relevant data. The following table outlines the access permissions to apps and features needed to fetch relevant data from Trend Vision API.

      Datastream Section Permissions
      Alert Platform Capabilities > Agentic SIEM & XDR > Workbench View, filter, and search.
      Audit Settings > Administration > Audit Logs View, filter, and search, Export and Download.
      Detection Platform Capabilities > Agentic SIEM and XDR > XDR Data Explorer View queries and Watchlist, and filter and search queries.
      Endpoint activity Platform Capabilities > Agentic SIEM and XDR > XDR Data Explorer View queries and Watchlist, and filter and search queries.
      Network activity Platform Capabilities > Agentic SIEM and XDR > XDR Data Explorer View queries and Watchlist, and filter and search queries.
      Telemetry Platform Capabilities > Agentic SIEM and XDR > XDR Data Explorer View queries and Watchlist, and filter and search queries.

      Refer to Account Role Permissions for more details.

    • Expiration time: The time the API key remains valid. By default, API keys expire one year after creation. However, a master administrator can delete and re-generate API keys at any time.

    • Status: Whether the API key is enabled.

    • Details: Extra information about the API key.

    Click Add.

  4. Copy the value of the API key.

Refer to First steps toward using the APIs for more details on setting up an API key.

Important

For the Telemetry data stream, which uses the Datalake Pipeline APIs, you need to allocate Trend Vision One credits for Data Transfer. For more information, see Credit requirements for Trend Vision One solutions, capabilities and services > Data Transfer.

When the Telemetry data stream starts for the first time it will use the Datalake Pipeline API to bind all telemetry data types to a new pipeline with a distinctive description. If a pipeline with that description already exists, it will be reused. It will never delete the pipeline, so if you stop using the integration, that pipeline should be removed manually.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

Elastic Agent is required to stream data from the syslog or log file receiver and ship the data to Elastic, where the events will then be processed using the integration's ingest pipelines.

  1. In the top search bar in Kibana, search for Integrations.

  2. In the search bar, type Trend Micro Vision One.

  3. Select the Trend Micro Vision One integration from the search results.

  4. Select Add Trend Micro Vision One to add the integration.

  5. Enable and configure only the collection methods which you will use.

    • To collect the logs from Trend Micro Vision One using API, you'll need to:

      • Configure Regional Domain URL and API Token.
      • Adjust the integration configuration parameters if required, including the Interval, Preserve original event etc. to enable data collection.
  6. Select Save and continue to save the integration.

  1. In the top search bar in Kibana, search for Dashboards.
  2. In the search bar, type Trend Micro Vision One.
  3. Select a dashboard for the dataset you are collecting, and verify the dashboard information is populated.

For help with Elastic ingest tools, check Common problems.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

This is the alert dataset.

This is the audit dataset.

This is the detection dataset.

This is the endpoint activity dataset.

This is the network activity dataset.

This is the telemetry dataset.

These inputs are used in this integration:

This integration dataset uses the following APIs:

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.