This Hotfix resolves the following issue(s):
An issue related to API keys may prevent the system from updating Trend Miro Apex One as a Service to Trend Vision One (Standard Endpoint Protection).
Solution
This Hotfix resolves the issue.
The system may include incorrect operating system information in logs when forwarding syslogs.
Solution
This Hotfix resolves the issue.
An issue related to DOS command processing is found in the system.
Solution
This Hotfix resolves the issue.
An issue related to dynamic file loading is found in the system.
Solution
This Hotfix resolves the issue,
This Hotfix resolves the following issue(s):
An issue related to maximum character limit and comments in Data Protection configuration may prevent the system from deploying or processing the configuration properly.
Solution
This Hotfix updates the Trend Micro Apex One Server and Security Agent program to resolve the issue.
An issue related to Trend Micro Apex One Central Agent service may cause the Trend Micro Apex One server to become unresponsive.
Solution
This Hotfix updates the Trend Micro Apex One Server program to resolve the issue.
Virtual Analyzer logs may contain incorrect execution time information.
Solution
This Hotfix updates the Trend Micro Apex One Server program to resolve the issue.
When resuming from sleep mode, an issue related to the Apex One Common Client Solution Framework service may cause the system to become unresponsive or encounter a Blue Screen of Death error.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
An issue may cause the Apex One common Client Solution Framework to become unresponsive.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
When switching between Data Loss Prevention (DLP) modes, the DLP pattern file may be removed and reverted to an older version.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
A hotfix update may prevent the system from restarting the Behavior Monitoring kernel driver to complete th driver upgrade process.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
The system may incorrectly detect outdated versions of .dll files in the Trend Micro Apex One agent package backup folder.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
There are no issues for this Hotfix release.
There are no enhancements for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix updates the Trend Micro Apex One Security Agent program to enhance protection for the PendingFileRenameOperations registry key.
This Hotfix enhances the Smart Protection Service Relay configuration update process to prevent redundant queries.
This Hotfix updates the Trend Micro Apex One Security Agent program to protect against a potential Local Privilege Escalation security issue.
This Hotfix updates the Virus Scan Engine (VSAPI) to version 25.610.1003 to enhance product capabilities.
This Hotfix updates the Trend Micro Apex One Server program to detect administrative operations with the correct system event type.
The following enhancements are included in this Hotfix:
This Hotfix updates multiple third-party libraries in Trend Micro Apex One (Mac) Security Agent to enhance product security.
This Hotfix updates the iCore module in Trend Micro Apex One (Mac) Security Agent to enhance product security.
This Hotfix enables Trend Micro Apex One (Mac) to send detection severity level information to Trend Micro Apex Central.
Security Agent version: 14.0.20521
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:
32-bit Security Agent Hotfix = 392 MB
64-bit Security Agent Hotfix = 527 MB
Security Agent Version: 3.5.8181
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/en-US/solution/KA-0011156)
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.