Certain specific paths cannot be added into the exception list of the Apex One Server from the policy setting page of the Apex Central console.

The device control list disappears from the policy deployment page of the Apex Central console after migration.

A case-sensitivity issue prevents Apex Central from generating reports successfully.

Chinese characters appear garbled in report email notifications.

The Windows Event Log is not triggered by a "Pattern file/Cleanup template update successful" event when the "Available Users and Groups list" is empty.

An error occurs when users add a user defined Suspicious Object (UDSO) through the AddUserDefinedSO API.

Apex Central sends outdated detection notifications.

The Application Control Server may not be able to handle criteria that have been exported and imported again.

The Application Control agent may not be able to start successfully if there is an incomplete agent registry key.

Sometimes, the "User Name" field in Data Loss Prevention(TM) (DLP) violation logs is empty.

An issue related to Smart Protection Servers may delay violation pop-up notifications on endpoints where the Security Agent is installed.

Users may not be able to save changes to the "Web Console Settings" page of the Apex One web console.

An issue related to the Behavior Monitoring module may cause the Trend Micro Unauthorized Change Prevention ("TMBMSRV.exe") service to stop unexpectedly.

The Trend Micro Apex One (Mac) agent Network Filter may experience interoperability issues which affect the performance of a protected Mac.

This Hotfix enables the Apex One Vulnerability Protection module to support up to 100 entries in the approved IP list.

This Hotfix extends the timeout value from 30 seconds to 180 seconds to help minimize SQL exceptions during Apex Central installation.

This Hotfix adds the following information in syslog:

• Apex Central Hostname
• A unique Message ID for each detection log
• Agent tree path

This Hotfix disables weak encryption protocols and enables Apex Central to support TLS 1.2 only. This change does not affect the on-premise Apex Central. For on-Premise Apex Central, follow the KB link below to evaluate if this update can be applied without service interruption. If the update has already been applied, set "m_strSSLCipherList = TLSv1.2" in "SystemConfigration.xml" to ensure that Single Sign-on (SSO) can go thorough TLSv1.2.

This Hotfix enables Apex Central to support Device Control Logs from Trend Micro Security for Mac(TM). On-premise Trend Micro Security for Mac installations require Trend Micro Security for Mac 2021 Patch 3 to support this enhancement.

Currently, when a user sends an isolation/restore isolation task through Apex Central, the page will display a message indicating that the command has been sent and is now wait for the agent to be notified. To refresh the status, users need to navigate away from the page and go back again.

This Hotfix applies the following changes to the All File Extension templates, including DLP Templates and DLP Data Identifiers, used in Apex One DLP:

1. The template will be removed for users that do not use it in any Apex One DLP Policy.
2. The template will be made customizable for users who use it in any Apex One DLP Policy.

This Hotfix adds a count-dependent log purge function to enhance the retention mechanism for Scan Operation Logs.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 21.550.1001.

This Hotfix updates the permission assignment process of the Apex One server program to enhance security.

This Hotfix updates the permission control feature of the Apex One Security Agent program to enhance security.

This Hotfix updates the command authentication mechanism of the Apex One server to enhance security.

This Hotfix updates the command authentication mechanism of the Apex One Security Agent to enhance security.

This Hotfix updates the Apex One Security Agent program to improve agent security.

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

This Hotfix enables Trend Micro Apex One (Mac) to officially drop support for macOS 10.11 (El Capitan) and macOS 10.12 (Sierra) from January 2022.

This Hotfix enables Trend Micro Apex One (Mac) to send Device Control logs to Trend Micro Apex Central(TM).

This Hotfix updates the Trend Micro Apex One (Mac) system requirements in the server document.

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.