Users do not receive event notifications if the log generation time field is empty.

Apex Central does not allow the number higher than 255 in the Fully-Qualified Domain Name (FQDN) of the SIEM server.

The "Policy Management" page loads repeatedly after users click the "Endpoints/Products without policies" count on the page.

Active Directory (AD) synchronization may fail because the mail column in the database is too small.

Active Directory synchronization is unsuccessful if the root domain of domain is unrecognition

The "%Hierarchy%" token does not display any information in email notifications.

After Trend Micro Apex One(TM) (Mac(TM)) registers to Apex Central, the "Product Component Status" field displays "No data to display".

An issue prevents the Policy Management screen from displaying properly.

File paths appear in the wrong format in syslogs.

Apex Central services stops unexpectedly.

The "Local Folder" node on the product tree can be expanded when users create an Active Directory (AD) account with the "DLP_Compliance_Officer" or "DLP_Incident_Reviewer" role.

Users do not receive C&C callback outbreak alert notifications.

The "Host Name" field in Behavior Monitoring Violations notifications displays the product server host name instead of the endpoint host name.

A high CPU usage issue occurs on the SQL server when purging Web Violations logs.

A performance issue causes an "Unable to execute SQL command. The database is busy. Try again after a few minutes." error in the "Historical Investigation" page of the Apex Central web console.

Users cannot search for targets to deploy policies by "Filter by Criteria" or "Specify Target(s)" in the "Policy Management" page.

The Product Directory page is affected by Cross-Site Scripting (XSS) issues.

Accounts in User Roles without a Policy Resource or Response permissions are logged-out of the web console after any of the following widgets are added into the first page of the Dashboard.

Top Violated Application Control Criteria Top Blocked Applications Attack Discovery Detections Top Endpoints Affected by IPS Events Top IPS Events Top IPS Attack Sources Vulnerability Protection

An Out-Of-Bounds Read vulnerability may cause the agent program to stop unexpectedly.

An issue prevents the Server Migration tool from importing the Trend Micro OfficeScan(TM) XG Service Pack 1 server settings to Apex One as a Service (AOSaaS).

Inaccurate date information displays in the "Last Firewall Count Sent" column on the "Agent Management" page of the web console.

The number of outdated agents on the Apex One dashboard is inaccurate because it receives the wrong outdated Antivirus component count. When users click the outdated agent count and navigate to the "Agent Management" page, the agent count on the page will also be inaccurate.

The Security Agent may cause a high memory usage issue on server platforms.

Known vulnerability issue found in the DebugManager tool.

This hotfix renames the "Host Name" field to "Endpoint" in unmanaged endpoints dataview.

This hotfix expands the IP address columns used in the Data Loss Prevention(TM) (DLP) violation log so that it can support the IPv6 address format.

This hotfix renames the "system restart required" action to "reboot system successfully".

This hotfix adds the new "Endpoint Sensor Activity Filtering Pattern" pattern.

This hotfix updates the Server Migration tool program to prevent binary version mismatch issues.

This hotfix enables Apex One to support Security Agent installation on the Microsoft(TM) Windows(TM) 10 May 2020 Update (20H1).

This hotfix enhances the performance of Apex One (Mac) as a Service.

When attempting to perform a Root Cause Analysis, the investigated email message may not be located due to synchronization delay with the Cloud App Security server and Office 365.

When attempting to perform a Root Cause Analysis, the investigated email message may be duplicated in the right panel while user clicks the the email message button.

A Root Cause Analysis report may not generate if the selected time range includes future dates.

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.

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 backslash (/) 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.