When the report file name is empty, the system does not purge the associated report data from the database.

Data Loss Prevention detection data from Apex Central is not displayed in red on the Trend Vision One console.

When there is no data displayed on the User/Endpoint Directory screen, the system does not generate the CSV file for data export.

Users receive an error message stating that they have not enabled Product Connector for Windows Events, even though the user does not use this feature.

An issue makes agent lost its specified Policy sometimes.

The version format of Application Reputation Lists in Apex Central is not correct.

An internal issue may prevent Apex Central from registering to Trend Vision One successfully.

After integrating with Trend Vision One, the system does not display the correct product name on the Trend Vision One console.

When users select the "UDP" protocol and click "Test Connection" on the Syslog Settings screen, the system displays the "Connection test is successful" message.

When an Apex One (Mac) server does not send the status information to Apex Central for an excessive amount of time, system automatically sets the Apex One (Mac) server status to "Inactive".

An issue related to AD synchronization may prevent AD users from logging into the Apex Central console.

An issue related to old component files used in Apex Central may expose system information.

The Client Authentication Checksum (CAC) security feature for server-agent communication may not function properly in Apex One.

Users may not be able to move selected Security Agent endpoints using the Standard Endpoint Protection app in Trend Vision One.

An issue related to the "Scan for Malware" feature in Trend Vision One may cause the Real-time Scan ("Ntrtscan.exe") service to stop unexpectedly.

An issue related to the Apex One Apex Central Agent ("OfficeScanCMAgent") service may prevent the Apex One server from updating the status logs of managed Security Agents to Apex Central properly.

After exporting the Security Agent list on the Agent Management screen in the Apex One web console, the "Data Protection Module" information is not included in the exported CSV file.

After migrating on-premises Apex One Security Agents to the SaaS version, the system displays the previous URL information for File Reputation Services feature on the Agent Management screen in the Apex One web console.

The system may not prevent protected Security Agent installation files on Security Agent endpoints from being modified.

After performing a Manual Scan on Security Agent endpoints, the system displays the "Interrupted by System" status for the scan operation.

The Trend Micro Unauthorized Change Prevention service ("TMBMSRV.exe") in Security Agents may result in a slow computer startup.

When Data Protection is enabled, Security Agents may incorrectly block non USB storage devices that are specified in the Approved Devices list.

Apex One (Mac) server may not deploy policies to newly-installed Apex One (Mac) Security Agents.

Go to Detections > Reports and enable "Report Maintenance".

This hotfix enables the system to not forward detection logs for specific Trend Micro products to their SIEM based on a filter.

This hotfix allows users to add the "ReportDateRangeType" flag in systemconfiguration.xml to determine whether the report date range is based on log generated time or log received time.

• 0 : generated time (default)
• 1 : received time

This hotfix displays the Application File version in Application Control detection logs.

This Hotfix adds Endpoint Host Name filter for the Suspicious File view on the Log Query screen.

This Hotfix adds support for ODBC Driver 17 for SQL Server in Apex Central.

This Hotfix updates Newtonsoft.Json to version 13.03.

This Hotfix updates the following third-party modules for PCI compliance:

• PHP: 8.2.12
• Curl: 8.4.0
• OpenSSL: 3.0.12
• NetSNMP: 5.9.4

This Hotfix allows the system to neutralize suspicious URLs in Web Violation View and notifications.

The hotfix adds a feature toggle that can let user to select certain product domain when creating report. And the default setting is off.

This Hotfix enhances the permission synchronization for Standard Endpoint Protection when creating or deleting groups on the Endpoint Inventory dashboard in Trend Vision One.

This Hotfix adds a prefix for synchronized accounts from Trend Vision One to prevent duplicate accounts when updating to Standard Endpoint Protection.

This Hotfix updates the Apex One Security Agent program to protect against a potential Local Privilege Escalation security issue.

This Hotfix updates the Apex One server program to protect against a potential Local Privilege Escalation security issue.

This Hotfix enhances the Security Agent update process to update Data Loss Prevention (DLP) templates from the Apex One server.

The Hotfix updates the event processing process in Apex One Security Agents to enhance the performance of the Web Reputation Service (WRS) feature.

This Hotfix resolves a Link Following Denial-of-Service security issue in the Apex One Security Agent program.

This Hotfix enhances the on-demand and real-time memory scans in Apex One Security Agent to protect against process memory scan attacks.

This Hotfix enhances the update process in Apex One to prevent excessive network bandwidth usage due to repeated agent updates and multiple component update downloads.

This Hotfix updates the Firewall Policy Exceptions screen in the web console to enhance user experience.

This Hotfix updates the copyright year in the Apex One (Mac) server and Security Agent consoles to 2024.

This Hotfix updates the iCore module in Apex One (Mac) Security Agent to enhance product integration.

This Hotfix updates Apex One (Mac) Security Agent to prevent incompatibility issues with the McAfee Data Loss Prevention program.

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.

A time zone issue may cause the system to display different log generation time information in the web console. In the web console, the system displays the log generation time in the time zone of the Apex One server.

• The Apex One server stores the log generation time information in GMT+0.
• The Security Agent sends the log generation time information (GMT+0 or local time) to the Apex One server.

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.