This Hotfix resolves the following issue(s):
Users are unable to search for endpoints.
Solution
This Hotfix resolves this issue.
If more than one server is selected, the system is unable to generate a scheduled report.
Solution
This Hotfix resolves this issue.
An issue prevents users from generating one-time or scheduled reports.
Solution
This Hotfix resolves this issue.
In forwarded syslog entries, the dvchost value is an internal environment code instead of the hostname.
Solution
This Hotfix resolves this issue.
Inaccurate Product Status information appear in Log Query results.
Solution
This Hotfix ensures that the correct Product Status information appears in Log Query results.
If the Approved_List section is configured in ADSyncOUList.config, Apex Central is unable to synchronize domains from Active Directory.
Solution
This Hotfix resolves this issue.
Two- factor authentication (2FA) is unsuccessful if user names do not contain more than three characters.
Solution
This Hotfix resolves this issue.
A Cross-Site Scripting vulnerability is found in the Policy Management module.
Solution
This Hotfix resolves this issue.
In Apex Central as a Service, an issue prevents the system from performing a backup successfully.
Solution
This Hotfix resolves this issue.
This Hotfix resolves the following issue(s):
When searching for endpoints on the Agent Management screen, the Apex One server does not update the "Offline Time" information properly for Security Agent endpoints.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
An issue related to the Security Agent proxy settings may prevent users from manually transferring or re-establishing communication between Apex One Security Agents and Apex One as a Service using the IPXfer Utility.
Solution
This Hotfix updates the Apex One server tool "IPXfer.exe" to resolve this issue.
When Data Loss Prevention (DLP) settings are configured in Security Agents to monitor sensitive data for printer devices, the system may generate false-positive Data Loss Protection alerts.
Solution
This Hotfix updates the Data Protection module to resolve this issue.
An issue related to the Location Awareness feature may prevent Security Agents from applying Smart Protection Server settings properly.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
This Hotfix resolves the following issue(s):
After upgrading an endpoint running on macOS 10.11 (El Capitan) or macOS 10.12 (Sierra) to a newer macOS version, the Apex One (Mac) Security Agent is unable to perform updates.
Solution
This Hotfix updates the agent macOS verification function in Apex One (Mac) to resolve this issue.
The following enhancements are included in this Hotfix:
This Hotfix removes two CEF keys (cs1 and cs1Label) and adds a new CEF key (TMCMLogTarget) to enhance the Behavior Monitoring syslog content.
This Hotfix enhances memory management to prevent LogRetriever.exe from becoming unresponsive.
This Hotfix adds a new CEF key (deviceDirection) in the C&C Callbacks syslog to indicate network traffic direction (1: Inbound or 2: Outbound).
This Hotfix updates the Data Loss Prevention Syslog feature to include log information for all DLP templates and DLP rules.
Apex Central can now synchronize Endpoint Sensor service status with the managed Apex One servers.
The following enhancements are included in this Hotfix:
This Hotfix updates the Inter-process communication (IPC) command authentication mechanism in Apex One Security Agent to enhance product security.
This Hotfix enhances the detection capabilities of the Predictive Machine Learning module and CVE exploit scanning to scan Microsoft Office files downloaded through web and email channels.
This Hotfix updates the ActiveUpdate (AU) module to version 2.86.4038 and the OpenSSL library in the module to version 1.1.1n to enhance product security.
This Hotfix updates the Anti-Spyware Engine (SSAPI) to version 6.2.1.4061 to prevent a potential Privilege Escalation security issue.
This Hotfix updates the Inter-process communication (IPC) command authentication mechanism for agent-server communication to enhance product security.
This Hotfix updates the Apex One Common Firewall Drivers to version 5.83.1086.
This Hotfix enables the telemetry monitor mechanism in Apex One to automatically generate and send logs for Apex One Security Agent restart events.
This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.1799.
This Hotfix updates the Advanced Threat Scan Engine (ATSE) to version 22.540.1001.
This Hotfix updates the OpenSSL library in Apex One to version 1.1.1n and the cURL binary to version 7.82.0 to enhance product security.
The following enhancements are included in this Hotfix:
This Hotfix adds the Trend Micro Cloud One Mac Agent module as a supplementary application.
This Hotfix adds the Scheduled Scan agent count information to the BIF feedback data.
Security Agent version: 14.0.11520
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.5953
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 213MB
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.