In some system logs, the "rt" CEF key value does not include the time zone information.

An internal issue in Apex Central may prevent users from importing policies successfully.

Potential Cross-Site Scripting (XSS) security issues are found in the Endpoint Encryption Plug-in in Apex Central.

Apex Central may not be able to deploy policies to managed Security Agents.

The system may return an incorrect error code for the List Security Agent API call.

After configuration, the access permission settings do not function properly.

The Active Directory synchronization tool may not work properly due to an issue in the protocol specification.

An issue on the edit account screen in the web console may truncate the account password resulting in unsuccessful user login attempts.

Apex Central is unable to deploy policies to Security Agents on endpoints running Windows 11.

A Server-side Request Forgery (SSRF) vulnerability is found in the Dashboard component.

A blue screen of death (BSOD) error may occur on Apex One Security Agent endpoints when the Suspicious Connection Service is enabled.

The Edge Relay server information may still exist in the system registry on Security Agent endpoints even when the Edge Relay feature is not available in Apex One as a Service.

When Data Loss Prevention (DLP) is enabled, Security Agents may not be able to detect and block files uploaded from removable storage devices.

An issue related to the the Apex One Apex Central Agent ("OfficeScanCMAgent") service may prevent Apex Central from deploying security policies to Security Agents through Apex One.

The Apex Central web console may display the "Abnormal" status for Apex One servers due to an issue related to the Apex One Apex Central Agent ("OfficeScanCMAgent") service preventing Apex One from updating the system status to Apex Central.

An issue related to the Application Control module may result in a slow application startup on endpoints.

This Patch adds the "SHA1" column for Predictive Machine Learning logs on the Log Query screen in the web console.

This Patch updates the Apex Central web console to include the "Policy Version" and "Last Edited" columns on the Policy Management screen for Apex One (Mac).

This Patch enhances user experience by hiding the "Allowed USB Devices" and "Allowed Programs" when the USB device privilege is set to read-only for Device Control policy configuration.

This Patch adds a new protocol filter value "TLS" on the Log Query screen for Suspicious Threats logs.

This Patch adds a new data identifier (Malaysia: NRIC - National Registration Identity Card Number) for Data Loss Prevention.

This Patch updates the related component to enhance integration with Apex One (Mac).

This Hotfix enables Apex One Security Agent to use encrypted text for Scan-Exclusions in registry entries on endpoints to enhance product security.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 22.610.1017 to support Advanced Malware Detection for well-known and high-volume malware sample scanning.

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

This Hotfix updates the third-party application uninstallation process (TmUninstall) in the Apex One Security Agent program to enhance product security.

This Hotfix enables support for Trend Vision One Endpoint Security migration.

This Hotfix updates theiCore module in Apex One (Mac) Security Agent to enhance system performance.

This Hotfix updates the legal documents for third-party components used.

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.