Apex Central may not send Data Loss Prevention (DLP) logs to the SIEM server.

A potential privilege escalation and cross-site script security issues are found in the Policy Management component in Apex Central.

The system may not display all managed Security Agents in the product tree or on the Policy screens in the Apex Central console.

The Trend Micro Unauthorized Change Prevention service ("TMBMSRV.exe") may stop unexpectedly.

The Trend Micro Data Loss Prevention add-on for Microsoft Outlook may stop unexpectedly and become disabled on Apex One Security Agent endpoints.

When performing process memory scan on Apex One Security Agent endpoints, the system may use an excessive amount of CPU or disk storage resource affecting system performance.

When the Apex One Firewall Service is enabled on Security Agent endpoints, Microsoft Office applications may become unresponsive or experience performance issues.

On Apex One Security Agent endpoints, the temporary folder size may be increased unexpectedly.

After uninstalling Apex One Security Agent on an endpoint, the Security Agent is not unregistered from Windows Security Center.

An issue related to the authentication mechanism for inter-process communication (IPC) commands in the Data Protection module may result in high CPU usage on Security Agent endpoints.

This Patch enhances the regular expression for the Taiwan: Name rule for Data Loss Prevention (DLP).

This Patch enhances Trend Vision One integration to improve detection log consolidation.

This Patch enhances Trend Vision One integration to improve Security Agent information update.

This Patch allows Apex Central to send vulnerability protection policy resource data to Trend Vision One to enhance vulnerability data visibility.

This Patch removes Dashboard widgets and policy resources associated with End-of-Service products to enhance user experience.

This Patch updates the jQuery library in Apex Central to enhance product security.

This Patch updates the PHP module in Apex Central to enhance product integration.

This Hotfix updates the Apex One Security Agent program to enable agent GUID synchronization with Endpoint Basecamp.

Note: For Security Agents whose GUIDs are updated during GUID synchronization, the system automatically removes related agent logs and set the Security Agents to use the default policy settings.

Trend Micro recommends you perform the following tasks:

• Before applying this Hotfix, back up agent logs.
• After applying this Hotfix, re-deploy policies to this kind of Security Agents.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 23.600.1002 to prevent a potential Improper Access Control Local Privilege Escalation security issue.

This Hotfix enables users to configure the automatic import of root certificates on protected Security Agent endpoints for file integrity checking based on the selected Windows platforms.

For more information, see the online help: "https://docs.trendmicro.com/en-us/documentation/article/apex-central-as-a-service-widget-and-policy-management-guide-global-agent-setting_006".

This Hotfix enables the Apex One Security Agent program to support endpoints running Microsoft Windows 11 23H2.

This Hotfix enables Apex One Security Agent to support the Generic Caching Service in Service Gateway for Trend Vision One integration.

This Hotfix includes the "Remove Domain/Agent" feature on the Agent Management screen in the Apex One web console for customers using Trend Vision One - Standard Endpoint Protection.

This hotfix includes proxy configuration for Smart Protection Service in Global Agent Settings for the following services:

• Predictive Machine Learning
• Behavior Monitoring

For more information, see the online help: "https://docs.trendmicro.com/en-us/documentation/article/apex-central-as-a-service-widget-and-policy-management-guide-global-agent-setting_006".

This Hotfix updates the PHP module in Apex One to version 8.2.11 to prevent a potential buffer overrun issue.

This Hotfix updates the OpenSSL library to version 3.0.12 and the cURL binary to version 8.4 in Apex One server and Security Agent programs to enhance product security.

This Hotfix updates the jQuery JavaScript Library in Apex One to version 3.6 to enhance product security.

This Hotfix enhances the self-protection feature in Apex One (Mac) Security Agent to prevent agent uninstallation by a third-party application.

This Hotfix adds the scrolling feature in the pop-up screen to enhance Device Control information display for Apex One (Mac) Security Agents.

This Hotfix updates the jQuery and PHP versions in Apex One (Mac) server to enhance product security.

Security Agent consoles running build 13.95 display an incorrect policy name. To resolve this issue, upgrade the Security Agent to 14.0. After the Security Agent contacts the server, the policy name displays correctly.

Off-premises and Security Agents in Independent mode cannot update the Certified Safe Software Pattern from external update sources.

Coexist mode Security Agents on endpoints with Windows Defender may experience installation issues or be unable to upload data to the Apex One server due to a file locking issue. To resolve this issue, add Endpoint Sensor (ESEServiceShell.exe and ESClient.exe) in the exclusions list of Windows Defender to prevent the locking issue.

After copying a file to a remote server using a relative path as the source, Apex One is unable to translate the relative path into the full system directory.

The quality of RCA analysis chain image files is reduced when viewing the files using Windows 10 Photo Viewer.

When attempting to start a Historical Investigation from the Attack Discovery Detections widget that includes Registry value name or Registry value data criteria, the Historical Investigation displays an error message if the length of the Registry value name exceeds 260 characters or the Registry value data exceeds 64 characters.

After updating the Attack Discovery Pattern file (tmesadp.ptn) on Security Agents, a database schema error may occur that causes the Endpoint Sensor feature to continuously report the same detections to the server during each synchronization. This causes duplicate records to display on the Apex Central server.

Root Cause Analysis email attachment results may also include temporary files created when the user saved the file.

The number of matched endpoints that display on a Root Cause Analysis chain may appear to be greater than the total if the Security Agent on an endpoint was uninstalled or no longer reports to the same managing server.

The Endpoint Sensor service may have high memory usage.

The Endpoint Sensor may have high peak CPU usage occasionally.

Endpoint Sensor has CPU peak during Windows Update phase.

The user or account name in ADE detection may be empty.

The EC module may stop responding while handling NULL data which may cause the ESEService and ADE functionality to behave abnormally.

In rare conditions, ESEService stops responding while unloading.

A time zone issue may cause the system to display different log generation time information in the web console. In the web console, the system displays the log generation time in the time zone of the Apex One server.

• The Apex One server stores the log generation time information in GMT+0.
• The Security Agent sends the log generation time information (GMT+0 or local time) to the Apex One server.

After enabling the Scan Time Machine option for Manual Scan and Scheduled Scan, Apex One (Mac) cannot perform any actions (clean, quarantine, or delete) on detected malware threats due to a permission limitation in Mac OS. Configured scan actions are displayed as unsuccessful in the product logs.

When performing a historical investigation on Apex One (Mac) endpoints, the system replaces a slash (/) with a colon (:) in file names, preventing users from searching for file names that contain backslashes in investigation results.

To resolve this issue, use a colon (:) to search for the files.