Use TrendAI as product name in trendmicro and trend_micro_vision_one integrations - #17045
Conversation
…integrations. In these integration's documentation and manifest titles and descriptions, rename "Trend Micro" to "TrendAI", as this is the new product name for the services these connect with. Also update the integration logo to the new product logo.
🚀 Benchmarks reportTo see the full report comment with |
|
@mjwolf is there any documentation from the Trend Micro side that suggests the use of TrendAI? When I check their site, I can still see these provides referred to as "Trend Vision One" and "Deep Security" - I worry about changing to TrendAI if that doesn't align with the actual product names. |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
@cpascale43 could you give us some insights on #15494 based upon @jamiehynds question? |
Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
|
Trend Micro are rebranding to TrendAI, we can wait on merging this until the change is public on their end though. |
|
Hi @mjwolf we can go ahead and merge this - looks like they are publicizing the name change. Ty! |
💚 Build Succeeded
History
|
|
Package trend_micro_vision_one - 2.10.1 containing this change is available at https://epr.elastic.co/package/trend_micro_vision_one/2.10.1/ |
|
Package trendmicro - 2.8.2 containing this change is available at https://epr.elastic.co/package/trendmicro/2.8.2/ |
Proposed commit message
In these integration's documentation and manifest titles and descriptions, rename "Trend Micro" to "TrendAI", as this is the new product name for the services these connect with.
Also update the integration logo to the new product logo.
Custom field names and integration name were not changed, as this would introduce breaking changes, so there will still be references to trendmicro in these integrations.
Checklist
changelog.ymlfile.