This Hotfix resolves the following issue(s):
The system may not replace the malicious URLs correctly in C&C callback notifications .
Solution
This Hotfix resolves the issue.
Users are unable to view Data Discovery logs for custom templates.
Solution
The Hotfix resolves this issue.
Incorrect file paths are displayed in Spyware/Grayware log query results.
Solution
The Hotfix resolves this issue.
User list truncated on Change Policy Owner.
Solution
The Hotfix resolves the issue.
On the Notification Settings screen in the web console, users are unable to specify the SMTP server FQDN with a dash ("-") in the domain name.
Solution
The Hotfix resolves the issue.
If there is an excessive number of user accounts, the system may take some time to display the User Account list in the web console.
Solution
The Hotfix resolves this issue.
A potential issue is found due to the exposed X-aspnet-version header.
Solution
This Hotfix removes the header to resolve the issue.
The samesite Lax setting is missing for the PHP_Session cookie.
Solution
This Hotfix adds the missing setting to resolve the issue.
This Hotfix resolves the following issue(s):
Running the uninstallation script may not uninstall the Apex One Security Agent program on endpoints.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
The Data Loss Prevention (DLP) detection logs may not include the complete USB storage device information.
Solution
This Hotfix updates the Data Protection module to version 6.2.5331 to resolve this issue.
When the Data Loss Prevention (DLP) settings are configured in Security Agents to monitor FTP file transfers for sensitive data, the system may generate false-positive DLP alerts for the WinSCP application.
Solution
This Hotfix updates the Data Protection module to version 6.2.5331 to resolve this issue.to resolve this issue.
In the Japanese version of Apex One, the system does not display a pop-up event notification for the Newly Encountered Program Protection feature for Behavior Monitoring.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
The Apex One Best Practice Guide Report does not provide an accurate compliance rate for Apex One Security Agent endpoints when the Trend Micro Vulnerability Protection agent (iVP) is enabled.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
When the Apex One Security Agent is enabled on a protected computer, the endpoint may become unresponsive or experience performance issues.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
Apex One Security Agent may not detect and block malicious programs that are launched by a PowerShell script.
Solution
This Hotfix updatesthe Behavior Monitoring Core Service module to version 2.98.2035 to resolve this issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix updates the internal process in Apex Central to enhance data synchronization with Trend Vision One.
This Hotfix adds AI App Guard policy feature and detection log in behavior Monitoring Log Query category.
This Hotfix adds a new monitoring process for Apex One services to enhance system performance.
The following enhancements are included in this Hotfix:
This Hotfix updates Security Agent Plug-in User Interface Manager to protect against a potential security issue (CVSS 3.0, Score 7.3).
This Hotfix updates the log forwarding function in Apex One to enhance the performance of detection log collection and processing.
This Hotfix adds a new "AI App Guard" policy setting for Apex One Security Agents to protect against malicious AI application tampering on endpoints.
This Hotfix enhances the Data Loss Prevention (DLP) templates to support Hong Kong ID card number detection and rectify a possible false-positive DLP alert.
This Hotfix updates the default Web Reputation approved list for new security policies.
There are no enhancements for this Hotfix release.
Security Agent version: 14.0.13260
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:
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.
There are no known issues for this Hotfix release.