After updating the Certified Safe Software Pattern, the Default Criteria - Assess Gray Software List Applications criteria for Application Control may not display, resulting in the need to reselect the criteria and redeploy the policy.

When a registered Apex One server is disconnected after applying a hotfix, the system continues to update the "Last Report" time of the Apex One server on the Server Registration screen.

The system uses the product code instead of the product name for the CEF key deviceFacility.

The system does not sort the users/endpoints list correctly after clicking the "Last Connected" column.

User accounts with a weak password may be at risk of being compromised through password guessing attacks.

An issue related to the product profile module causes the web console to display an empty Component List.

Changing the root domain name unexpectedly starts the filtering function in the Active Directory synchronization tool.

A database deadlock issue is found in the policy management module.

When configuring IP address auto label rules on the Label Settings screen, the system does not check the IP address range format.

When Data Loss Prevention (DLP) is enabled on Apex One Security Agent endpoints, Google Chrome (version 106 or later) and Microsoft Edge (Chromium) may become unresponsive.

After moving an Apex One domain to a parent domain, the Apex One server does not synchronize the domain information properly with Apex Central.

An issue related to the Web Reputation Service (WRS) may prevent users from connecting to Captive Portal Wi-Fi properly. When this happens, users are not granted the permissions to access network resources.

The Apex One Firewall Service may not be installed properly on Apex One Security Agent endpoints.

This Hotfix supports the import of Application Control hash value criteria without the file path in CSV files.

This Hotfix enhances the Single Sign-on (SSO) feature to improve user experience.

This Hotfix enables the Apex One Security Agent program to support Microsoft(TM) Windows(TM) 11 (version 22H2) 2022 Update.

This Hotfix updates the OpenSSL library in Apex One to version 3.0 and the cURL binary to version 7.84 to enhance product security. For more information, see "https://success.trendmicro.com/solution/000291701".

This Hotfix updates the Data Protection module to version 6.2.5173 to enhance the digital signature integrity checking process.

This Hotfix updates the Damage Cleanup Engine to version 7.5.1184 to resolve a Local Privilege Escalation security issue.

This Hotfix updates the open-source 7-Zip application in Apex One to version 22.01 to enhance product security.

This Hotfix enhances the Issuer Information Checking mechanism in Apex One Security Agent to enhance product security.

This Hotfix updates the Trend Micro URL Filtering Engine in Apex One Security Agent to version 5.0.1032 to resolve a Link Following Privilege Escalation security issue.

This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.1873, the Program Inspection Engine to version 2.9.1043, and the Trend Micro User-Mode Hook Event module in Apex One Security Agent to version 8.55.1129 to improve support for Security Agent product compatibility.

This Hotfix enables Trend Micro Apex One (Mac) to officially stop supporting macOS 10.13 (High Sierra) after November 2022.

This Hotfix enables the Apex One (Mac) Security Agent program to support macOS 13 (Ventura).

This Hotfix updates the Trend Micro Apex One (Mac) system requirements on the Online Help Center.

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.