Apex Central may send duplicate C&C Callback syslogs to the SIEM server.

Users cannot Single Sign-On (SSO) to the Apex one web console from the Apex Central web console.

Apex Central may take an excessive amount of time for policy deployment.

Apex Central may not send detection logs and endpoint information to Trend Vision One.

An issue related to the server GUID length may prevent Apex Central from displaying assessment results from Apex One on the Historical Investigation screen.

An issue related to the timestamp provided through API calls in the syslog may prevent Splunk from displaying related event information on the console.

During Active Directory synchronization, the system may unexpectedly filter data from approved organizational units (OU).

The system may generate logs that cannot be manipulated on the DLP Incident Information screen.

Widgets on the Dashboard may be exposed to potential Cross-Site Scripting (XSS) vulnerabilities.

An issue related to the Application Control agent may result in a slow application startup.

Some third-party applications may not work properly on Apex One Security Agent endpoints when Apex One Firewall is enabled.

On the Log Query screen, the system always displays the "Global C&C Pattern" status in the "Pattern Type" column for Network Content Inspection logs for User-Defined Suspicious Object detections.

An issue related to the file cleanup function in Apex One Security Agent may result in an excessive amount of temporary update files in the "AU_Temp" folder on Security Agent endpoints.

The system may display the "System error. Error ID: 5" policy status even when security policies are deployed to managed Security Agents successfully.

Users are unable to add a USB device to the allowed list when the system displays special characters for the USB device serial ID in the Device List Tool (listDeviceInfo.exe).

This Hotfix enhances the Users/Endpoints > Endpoints screen to display the OS Version column.

This Hotfix adds cookies to enhance Apex One server login authentication and optimize System Event Logs for login events.

This Hotfix updates error codes in Apex Central to enhance the error message for Apex One (Mac) server configuration.

This Hotfix enhanced the Apex Central web console to include a tooltip for the Application Reputation List on Application Control Criteria screen.

This Hotfix enhances the security agent status synchronization process to improve system performance.

This Hotfix enhances the CommandTracking function in Apex Central to improve system performance.

This Hotfix enhances the Smart Feedback feature for comprehensive targeted detection scans and automatic notifications.

This Hotfix adds environment pre-checking in the Apex One server and Security Agent installation package (MSI) to support certificate integrity checking for Azure Code Signing (ACS).

This Hotfix enhances the Smart Feedback feature in Apex One to offer state-of-the-art scanning for targeted attack indicators and automated notifications of potential threats to your environment. For more information, see "https://success.trendmicro.com/dcx/s/solution/000292353".

This Hotfix enables Apex One to support Client Authentication Checksum (CAC) security for server-agent communication.

This Hotfix updates the OpenSSL library to version 3.0.7 and the cURL binary to version 7.86 for integrated Trend Micro modules in the Apex One server and Security Agent programs to enhance product security.

This Hotfix updates the Data Protection module to version 6.2.5194 and enables the Data Loss Prevention (DLP) module in Apex One Security Agent to monitor file movements in Microsoft™ Outlook on endpoints.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 22.610.1007 to support well-known and high-volume malware sample scanning.

This Hotfix updates the Apex One Client Plug-in Service Manager module to protect against the Time-of-Check Time-of-Use Local Privilege Escalation vulnerability.

This Hotfix updates the Apex One server program to protect against the System Privilege Exploiting Path Traversal vulnerability.

This Hotfix enables Security Agents to send Device Control event information (device vendor, model, and serial ID) to Apex Central.

This Hotfix updates the Security Agent program to prevent against a potential memory leak issue in the TMCNTMgmt process.

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.

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.