feat: add parser for Trend Micro Vision One Risk Events

[wentao-trendmicro]

Summary

• Add community parser for TRENDMICRO_VISION_ONE_RISK_EVENTS log type
• Parses Trend Micro Vision One risk event logs into UDM format
• Maps risk scores to severity levels (CRITICAL/HIGH/MEDIUM/LOW/INFORMATIONAL)
• Maps resolve flags (new, accepted, resolved, close, system_remediation, system_remediated) to security actions
• Extracts principal, target, cloud, and additional fields from risk event data

Test plan

• Validate parser against sample risk event logs
• Verify UDM field mapping correctness
• Pass "Validate Parsers" automated check
• Pass "Validate Google & Parsers" SecOps instance check

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new community parser for Trend Micro Vision One Risk Event logs. The parser enables the transformation of these logs into the Unified Data Model (UDM) format, facilitating better security visibility by mapping risk-specific data points such as severity levels, security actions, and various cloud and asset-related metadata.

Highlights

• New Parser Implementation: Added a community parser for Trend Micro Vision One Risk Events to support log ingestion and normalization.
• UDM Mapping: Implemented comprehensive mapping for risk scores to severity levels and resolve flags to security actions.
• Data Extraction: Configured extraction for principal, target, and cloud-related fields, including dynamic parsing of metaInfo.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request introduces a new parser for Trend Micro Vision One Risk Event logs, including the Logstash configuration, metadata, and test data. The review identified two critical issues in the Logstash configuration: first, converting riskScore (which can be a float) directly to an integer will cause failures, so it should be converted to a float instead; second, nested fields within the parsed JSON (such as meta.appName) must be referenced using bracket notation (e.g., %{[meta][appName]}) rather than dot notation, and should be protected with if guards to avoid mapping literal template strings when the fields are missing.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.