This Hotfix resolves the following issue(s):
When accessing the Trend Micro Apex Central web console through Standard Endpoint Protection in Trend Vision One, the system logs out users unexpectedly.
Solution
This Hotfix resolves the issue.
Canceling an in-progress component download and then triggering a manual Download Now task might cause the manual download to fail.
Solution
The issue is resolved.
The Static Report Template "Threat detections by channel and product" report displays an incorrect percentage.
Solution
The issue is resolved.
There are vulnerabilities in the PHP module.
Solution
PHP has been upgraded to version 8.2.29 to enhance product security.
An issue may prevent Trend Micro Apex Central from synchronizing suspicious object lists successfully from Trend Vision One.
Solution
This Hotfix resolves the issue.
User cannot pre-deploy policies in the offline installation package on Trend Vision One.
Solution
This hotfix resolves the issue.
After deleting a policy, the deleted policy reappears.
Solution
This hotfix resolves the issue.
This Hotfix resolves the following issue(s):
An issue related to displaying incorrect Behavior Monitoring log numbers on the dashboard when the log number is zero.
Solution
The hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
When the option "Agents use the proxy server settings configured in Windows Internet Options when connecting to Trend Micro servers," is enabled, the agent does not maintain the configured value after performing an agent update.
Solution
The hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
Behavior Monitoring alerts display when launching a Microsoft application.
Solution
The hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
An issue related to the agent repeating the update progress and is unable to be stopped.
Solution
The hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This hotfix will hide the following pages and APIs when Trench Micro Apex Central connects to Trend Vision One:
Added a destination (dst) field to data_loss_prevention Log Query API.
The following enhancements are included in this Hotfix:
This hotfix updates Product Licensing Management to 2.5.6220. This upgrades PHP to 8.2.29 to enhance product security.
This hotfix enhances product security by updating the PHP module in Trend Micro Apex One to version 8.2.29 and rebuilding/updating PHPExtension using the new PHP version.
The hotfix updates the 7-Zip module in Trend Micro Apex One to version 25.1 to enhance product security.
The following enhancements are included in this Hotfix:
This Hotfix updates the Trend Micro Apex One (Mac) Security Agent program to enhance integration with Trend Vision One.
This Hotfix updates multiple third-party libraries in Trend Micro Apex One (Mac) Security Agent to enhance product security.
Version: 7126
Security Agent version: 14.0.20225
Security Agent restart: Yes
Security Agent OS reboot: Not required for Security Agents are running build versions later than 10000.
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.8072
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 271MB
Additional Requirements: Enable web browser extension (https://success.trendmicro.com/solution/000273346)
No post-installation steps are required.
NOTE: Trend Micro recommends that you update your scan engine and virus pattern files immediately after installing the product.
There are no known issues for this Hotfix release.
Known issues in this release:
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.
Known issues in this release:
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.