This Hotfix resolves the following issue(s):
Users with "Read-Only" privileges can modify the Apex One settings after accessing the Apex One console through Single Sign-On (SSO).
Solution
This Hotfix ensures that only accounts with the required privileges can be used to modify the Apex One settings.
The general information about certain security threats do not display normally on the Control Manager web console.
Solution
This Hotfix resolves this issue.
The Data Loss Prevention(TM) (DLP) module does not accept some valid regular expressions on the Control Manager web console.
Solution
This Hotfix resolves this issue.
The "cs5" CEF key displays a numerical value instead of a meaningful string in Content Security Logs.
Solution
This Hotfix ensures that the correct information appears in Content Security Logs.
An issue prevents Apex Central from forwarding Web Violation Logs to the SIEM server.
Solution
This Hotfix resolves the issue so Apex Central can forward Web Violation Logs to the SIEM server normally.
One-time reports generated with custom templates do not follow the specified time period.
Solution
This Hotfix ensures that custom one-time reports display events that occur in the specified time period.
When users search for endpoints on the "User/Endpoint Directory" page, the search results display only up to 15 endpoints.
Solution
This Hotfix ensures that all endpoint search results display normally on the "User/Endpoint Directory" page.
This Hotfix resolves the following issue(s):
Apex One Security Agents may appear "Offline" after the security agent is connected to the network through VPN.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
An issue may cause the Dashboard of the Apex One Management Console to respond slowly.
Solution
This Hotfix updates the Upgrade SQL Schema to resolve the issue.
Apex One Security Agents still upload Firewall logs to the Apex One server when the "Send firewall log count information to the Apex One server hourly to determine the possibility of a firewall outbreak." setting is disabled on the "Global Agent Settings\Firewall Settings" page of the Apex One web console.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
A signature checking issue related to the Trusted Programs List may cause the Apex One NT RealTime Scan ("Ntrtscan.exe") service to stop unexpectedly.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
An issue related to the Data Loss Prevention(TM) (DLP) exclusion settings may cause the Apex One NT RealTime Scan ("Ntrtscan.exe") service to stop unexpectedly.
Solution
This Hotfix updates the Data Protection module to resolve this issue.
A buffer overrun issue may cause the Apex One NT Listener service ("TmListen.exe") to stop unexpectedly. When this happens, the Apex One Security Agent is not able to update pattern files successfully.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
A Digital Signature checking issue related to the Data Protection module may prevent Apex One Security Agents from updating the Apex One Security Agent program properly.
Solution
This Hotfix updates the Data Protection module to resolve this issue.
Unnecessary files on some Japanese version installations of Apex One as a Service may prevent users from upgrading Security Agents from Trend Micro OfficeScan(TM) XG or XG Service Pack 1.
Solution
This Hotfix resolves this issue by updating the Apex One server files.
This Hotfix resolves the following issue(s):
When the uninstaller is downloaded through a web browser, it may not be able to gain user authority on macOS 10.15 or any lower version.
Solution
This Hotfix updates the uninstaller to resolve this issue.
Full Disk Access cannot be verified successfully if only "iCoreService" is added to the program list on macOS 11.4.
Solution
This Hotfix adds "iCore Service.app" into the Full Disk Access program list to resolve this issue.
The "Unable to start Apex One (Mac) Security Agent" popup message displays on the Apex One for Mac Agent when the value of "lookup_server" is null.
Solution
This Hotfix resolves the issue by setting a default value for "lookup_server".
The Blocked List remains in agent machines after it is removed from the server.
Solution
This Hotfix resolves the issue by updating the Apex One for Mac Server Web Threat Protection module.
The following enhancements are included in this Hotfix:
This Hotfix extends the supported range of Discover and Maestro Credit Card Numbers in Control Manager.
This Hotfix adds the following two custom CEF keys for all detection logs except for Content Violations and Application Control logs.
The following enhancements are included in this Hotfix:
This Hotfix updates the Apex One Security Agent program to prevent a potential security issue.
This Hotfix updates the permission control feature of Apex One agents to improve security.
The following enhancements are included in this Hotfix:
This Hotfix updates the pattern in the Apex One (Mac) agent installer to reduce download traffic.
Security Agent version: 14.0.9619
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.5255
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 187MB
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.