Collect Trend Micro Vision One Observed Attack Techniques logs

This document explains how to ingest Trend Micro Vision One Observed Attack Techniques logs to Google Security Operations using AWS S3. The parser transforms the logs from JSON format into a Unified Data Model (UDM).

Before you begin

Make sure you have the following prerequisites:

• Google SecOps instance
• Privileged access to Trend Micro Vision One

Configure Logging on Trend Micro Vision One

1. Sign in to the Trend Micro Vision One console.
2. Go to Workflow and Automation > Third-Party Integration.
3. Click Google Security Operations SIEM.
4. Under Access key, click Generate key.
5. Copy and save the access key ID and secret access key.
6. Under Data transfer, enable the toggle next to Observed Attack Techniques.
7. An S3 URI is generated and the data begins to be sent to the corresponding S3 bucket.
8. Copy and save the S3 URL for use at a later time.

Set up feeds

To configure a feed, follow these steps:

1. Go to SIEM Settings > Feeds.
2. Click Add New Feed.
3. On the next page, click Configure a single feed.
4. In the Feed name field, enter a name for the feed (for example, Trend Micro Vision One Observed Attack Techniques Logs).
5. Select Amazon S3 V2 as the Source type.
6. Select Trend Micro Vision One Observed Attack Techniques as the Log type.
7. Click Next.

8. Specify values for the following input parameters:

   • S3 URI: The bucket URI (the format should be: s3://log-bucket-name/). Replace the following:
     • log-bucket-name: the name of the bucket.
   • Source deletion options: Select Never delete files. Data in the S3 bucket is retained for 7 days before being purged.
   • Maximum File Age: Includes files modified in the last number of days. Default is 180 days.
   • Access Key ID: User access key with access to the S3 bucket.
   • Secret Access Key: User secret key with access to the S3 bucket.

9. Click Next.

10. Review your new feed configuration in the Finalize screen, and then click Submit.

UDM mapping table

Need more help? Get answers from Community members and Google SecOps professionals.