Rebranding rollout
The TrendAI™ branding update for TrendAI Vision One™ Endpoint Security agents is being introduced progressively:
- The agent console UI began reflecting the updated TrendAI™ branding with the March 2026 rollout. Additional agent component updates are scheduled to be deployed starting June 2026.
- As updates are applied over time, endpoints may display different branding states during the transition period.
Expected behavior during rollout
During the phased rollout, variations in branding may be observed across endpoints. For example:
- Endpoints within the same environment may display different branding depending on their current update status. Updated branding will appear gradually as additional agent updates are applied over time.
- These variations are expected during the rollout period and do not indicate an issue with the agent.
What You Need to Do
Endpoint agents will automatically reflect the updated branding as updates are applied.
However, if your environment uses third-party network access control (NAC), VPN, or endpoint posture solutions, additional action may be required to prevent endpoints running Apex One as a Service agent build 14.0.20842 or later from being flagged as non-compliant.
Take the action that corresponds to your posture solution:
Cisco ISE
Update your ISE posture policy to recognize "Apex One Security Agent" as the display name and/or the updated agent service name. Retaining the previous entry ("Trend Micro Apex One Security Agent") alongside the new one ensures coverage for endpoints on either build during the transition period.
Palo Alto Networks GlobalProtect (via OPSWAT)
Apply the latest OPSWAT definition file on the GlobalProtect side. The updated file maps the new "Apex One" product name and restores compliant detection.
F5 BIG-IP Edge Client (via OPSWAT)
Apply the OPSWAT definition file dated June 15, 2026, or later on F5 BIG-IP. This version has been confirmed to resolve the AV-compliance check failure.
TrendAI™ Zero Trust Secure Access (ZTSA)
Upgrade ZTSA to v2.35.1036 or later. This release restores correct recognition of the Security Agent.
Controlling the timing of agent upgrades (optional)
Apex One as a Service agents upgrade to the latest maintenance build automatically by default. If you wish to control upgrade timing — for example, to allow time for posture definition updates to be applied first — you can pin or freeze the agent version using the Program Update policy setting. Refer to knowledge article KA-0014555 for step-by-step instructions. Note that the Apex One SaaS agent does not support one-click rollback; managing upgrade timing via policy is the recommended approach.
If you are not using any of the above solutions and have not observed VPN or network access issues, no action is required.
