This Hotfix resolves the following issue(s):
Users encounter an internal server error while searching for specific users or endpoints in the "User/Endpoint Directory" page.
Solution
This Hotfix ensures that users can search for specific name or endpoints in the "User/Endpoint Directory" page normally.
When configuring policies, users were unable to sort Active Directory as a criteria option.
Solution
The issue has been resolved.
The search results on the "DLP Incident By User" widget do not accurately apply the selected time range.
Solution
The issue has been resolved.
The Server Registration / Product Server screen may display the server IP address instead of the server URL.
Solution
The default display of the Server URL has been updated to the server name ( FQDN / Hostname ) first and then the IP address.
Summarizing the Data Loss Prevention Log may consume an unexpected volume of SQL Server CPU resources.
Solution
The summarizing process has been updated to reduce the CPU resource consumption.
The "Product Events" logs on Log Maintenance are not purged daily .
Solution
This Hotfix resolves this issue.
"CmdProcessor.exe" may not release some memory blocks or handles promptly after completing certain actions such as component updates.
Solution
This Hotfix improves resource management and memory/handle cleanup for "CmdProcessor.exe" to prevent this issue.
This Hotfix resolves the following issue(s):
Data Loss Prevention(TM) (DLP) policies applied to Security Agents may not function properly due to an incorrect buffer size setting in the Data Protection module.
Solution
This Hotfix updates the Data Protection module to resolve this issue.
Apex One Security Agents may incorrectly block allowed USB storage devices when the Data Protection service is enabled.
Solution
This Hotfix updates the Data Protection module to resolve this issue.
Security Agents with Data Loss Prevention enabled may not properly detect and block uploads to websites.
Solution
This Hotfix updates the Data Protection module to resolve this issue.
In some Japanese versions of Apex One as a Service, an unnecessary "epasopt" user account may display in the System Event Logs of the Apex One web console.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
The Device List Tool (listDeviceInfo.exe) may not correctly retrieve certain camera device information.
Solution
This Hotfix updates the Data Protection module and Device List Tool (listDeviceInfo.exe) to resolve this issue.
Apex One Security Agents may appear "Offline" after disabling proxy settings and connecting to the network directly.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
An Incorrect Permission Assignment Privilege Escalation Vulnerability may allow an attacker to modify a specific script before it is executed on a protected computer.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This release supports the following new components: -- Damage Cleanup Engine (Universal) -- Virus Scan Engine (Universal) -- Advanced Threat Scan Engine (Universal)
This Hotfix reduces detailed step logs when "LogProcessor.exe" is on debug mode.
The following enhancements are included in this Hotfix:
This Hotfix updates the Apex One server program to restrict the access permission requirement for the backup folder to prevent a potential security issue.
This Hotfix updates the Apex One program to prevent a potential security issue.
This Hotfix updates the Apex One program to harden the communication pipes and enhance security.
The following enhancements are included in this Hotfix:
This Hotfix enables the Apex One (Mac) Security Agent program to support the Apple(R) M1 chip.
Security Agent version: 14.0.9672
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.5314
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 207MB
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.
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.