There are no issues for this Hotfix release.
This Hotfix resolves the following issue(s):
When the Data Loss Prevention (DLP) settings are configured in Security Agents to monitor Yahoo Mail messages for sensitive data, the system may generate false-positive DLP alerts.
Solution
This Hotfix updates the Data Protection module to version 6.2.5221 to resolve this issue.
For sample submissions to Deep Discovery Analyzer, the system does not display Apex One as a submitter on the Deep Discovery Analyzer management console.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
After performing a component update, the system displays "Outdated" for the status of the Web Reputation Endpoint Patch Pattern component on the web console.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
After configuring the required information for Smart Feedback to enable the Targeted Attack Detection (TAD) function, the system displays an error.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
The Trend Micro Apex One Data Protection service ("DSAGENT.exe") may stop unexpectedly.
Solution
This Hotfix updates the Data Protection module to version 6.2.5221 to resolve this 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 removes some local signature files in Apex One to enhance product security.
This Hotfix updates the Apex One Security Agent program to protect against potential Local Privilege Escalation vulnerabilities.
This Hotfix updates the Advanced Threat Scan Engine (ATSE) to version 22.610.1017 and the Trend Micro xHandler module to version 1.200.1015 to support well-known and high-volume malware sample scanning.
This Hotfix enhances the log forwarding function for system event logs to improve log collection performance in Apex One.
This Hotfix enhances the log forwarding function for Security Agent detection logs to improve log collection performance in Apex One.
This Hotfix enhances the log forwarding function for Security Agent IP address check to improve log collection performance in Apex One.
This Hotfix enhances the system reliability of the Apex One server by adding the agent GUID check mechanism to check for invalid Security Agents.
There are no enhancements for this Hotfix release.
Security Agent version: 14.0.12518
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
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.
There are no known issues for this Hotfix release.