The system is unable to generate scheduled reports.

After manually deploying a policy by clicking "Deploy", the keyword for the Apex One Domain Hierarchy policy filtering criteria is modified unexpectedly.

The system may not display newly created endpoint groups in Endpoint Inventory in Trend Vision One.

The system is unable to move selected endpoints to a newly created endpoint group in Endpoint Inventory in Trend Vision One.

When users do not have permission for a product instance in Standard Endpoint Protection, the system still displays the associated endpoints in Endpoint Inventory in Trend Vision One.

After updating to Standard Endpoint Protection, the system may generate scheduled reports that contain no data.

The system may display the incorrect user information in the policy owner list or contact group list.

The system is unable to obtain log information using the syslog API.

An issue related to the multi-factor authentication module may prevent users from logging into the web console.

There is a mismatch of "Antivirus Pattern Compliance" percentage information in the Security Posture widget in the web console.

Users are unable to add URL objects containing curly brackets {} to the User-Defined Suspicious Object list in the web console.

Potential vulnerabilities are found in the Java Runtime Environment (JRE) module used in Apex Central.

The system may not display Predictive Machine Learning detection logs in log query results.

An issue related to the Apex One Master Service ("ofcservice") may prevent Apex One from performing scheduled tasks normally.

The system may not display the search results for Data Discovery logs from Apex Central on the Log Query screen.

Ans issue related to the Trend Micro Vulnerability Protection agent may prevent the system from installing a third-party VPN program on Apex One Security Agent endpoints.

The Apex One Data Loss Prevention (DLP) service may not function properly in Google Chat or Google Spaces.

The system may not display status of the Vulnerability Protection feature properly on the Console Flyover menu in the Security Agent console.

After installing Apex One Security Agent on an endpoint, the system may not start the Apex One Data Protection Service properly.

An issue related to the file name validator checking mechanism in Apex One may prevent Apex One Security Agents from sending violation detection logs to the Apex One server properly.

An issue related to proxy server connection in Apex One Security Agent for Trend Vision One integration may result in a slow computer startup.

This Hotfix adds the new "Action" column for C&C Callback log query result display to enhance data visibility.

This Hotfix updates the Apex One (Mac) widget to protect against the Remote Code Execution security issues.

This Hotfix enables Apex Central to generate historical records of managed Security Agents.

This Hotfix updates the Virus Scan Engine to protect against the Link Following Local Privilege Escalation security issue (ZDI-CAN-22693)(CVSS 3.0, Score 7.8).

This Hotfix updates the Virus Scan Engine to protect against the Link Following Information Disclosure security issue (ZDI-CAN-22032)(CVSS 3.0, Score 4.7).

This Hotfix updates Security Agent Plug-in User Interface Manager to protect against a potential security issue (CVSS 3.0, Score 7.3).

This Hotfix updates the widget component to protect against the Local File Inclusion and Remote Code Execution security issue (ZDI-CAN-23401)(CVSS 3.0, Score 7.5).

This Hotfix adds support for Intel® Threat Detection Technology (Intel® TDT) to enhance the performance of memory process scanning at the hardware level.

This Hotfix updates the Scheduled Updates configuration process for hourly update frequency for Security Agents to enhance user experience.

This Hotfix updates Apex One Security Agent policy configuration in Apex Central to include Scan Settings for Large Compressed Files and Scheduled Scan Settings for Anti-malware Scan settings.

Note: If the Apex One as a Service server is registered to an on-premises version of Apex Central, this update requires the installation of Apex Central Patch 8 build 8.0.0.6796 or above. For more information, see "https://success.trendmicro.com/dcx/s/solution/000298004".

This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.2012 to enhance product security.

This Hotfix updates the Newtonsoft.Json module in Apex One (Mac) to enhance product security.

This Hotfix updates the core module of the Apex One (Mac) Security Agent program to enhance system performance.

This Hotfix updates the log level of the Apex One (Mac) server to enhance system performance.

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.