The system may not display the matching results for DLP templates in the web console.

An issue related to empty rule content in Trend Micro Apex Central may cause the Application Control process (PolicyUpdater.exe) to be unresponsive.

Potential SQL injection vulnerabilities are found in the Trend Micro Apex One (Mac) widgets.

The system displays an inappropriate rule name for a web violation detection.

When no parent node is selected, the system may not display log query results for web violation logs in the web console.

Potential vulnerabilities related to access control for the Dashboard and widget components are found in Apex Central.

The system may not properly display the "samlGroupSeamless" parameter value in the web console.

An issue related to log processing may cause the system to display "N/A" for the log description.

A key value that control role permissions is not updated causing some UI in Apex One console to always be grayed out.

Apex Central sends User-Defined Suspicious Objects with an incorrect expiration date to Apex One.

Data Loss Prevention (DLP) may not function properly for compressed files.

An issue related to the Trend Micro Security Agent Monitor ("PccNTMon.exe") process may cause the process to appear as duplicated and may affect system performance on Security Agent endpoints.

The "Scan for Malware" feature in Trend Vision One may not work on Security Agent endpoints.

After installing Apex One Security Agent on an endpoint with Smart Scan mode, the Security Agent icon may show Conventional Scan mode in the Microsoft(TM) Windows(TM) task bar.

When the Trend Micro Apex One Security Agent is offline, disabled, or uninstalled, the Security Agent may send the “snoozed” status to Windows Security Center.

The Data Protection service ("DSAGENT.exe") may not be installed properly on Trend Micro Apex One Security Agent endpoints.

An issue related to the Data Protection service ("DSAGENT.exe") may cause Trend Micro Apex One Security Agent to incorrectly block file transfers through SAP GUI.

Trend Micro Apex One Security Agent may not detect and block potentially malicious files that are launched from Microsoft OneDrive cloud storage.

An issue related to the Trend Micro Apex One web console may prevent users from reordering the Firewall Policy Exceptions.

An issue related to Predictive Machine Learning for file detections may cause Trend Micro Apex One Security Agent to incorrectly block the powershell script that is used for remote server PowerShell connections.

This Hotfix adds the "Rule ID" and "Policy Name" columns for the following detection log queries to support policy exclusions by rule IDs:

• Virus/Malware
• Behavior Monitoring
• Network Content Inspection

This Hotfix supports monitoring levels for Endpoint Protection features, providing a flexible and customizable approach to balancing noise and detections. This allows you to optimize your security posture based on your organization's needs and requirements.

This Hotfix updates the ActiveUpdate (AU) component.

This Hotfix adds a new setting to block untested URLs in Web Reputation policies for Apex One (Mac).

The Standard Endpoint Protection Server no longer supports displaying Tracked Endpoints in the User/Endpoint Directory.

This Hotfix enables Trend Micro Apex One Security Agent to detect potential remote ransomware and block the SMB port (port 445) on the endpoint. The system will automatically unlock the SMB port after one hour (default).

NOTES:

1. The Remote Ransom feature is enabled by default.

• 32-bit: \HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Real Time Scan Configuration
• 64-bit: \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Real Time Scan Configuration
• Key: EnableRRD
• Type: DWORD
• Value: 1

2. The block interval for the SMB port is 60 minutes by default.

• 32-bit: \HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Real Time Scan Configuration
• 64-bit: \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Real Time Scan Configuration
• Key: RRD_BlockSMBInterval
• Type: DWORD
• Value: 60

3. To unlock the SMB port on an agent endpoint immediately, unload and reload the Security Agent.

This Hotfix enhances cloud storage reclassification for Security Agents with Data Loss Prevention enabled.

This Hotfix adds a new setting to block untested URLs in Web Reputation policies for Apex One (Mac).

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

This Hotfix enables the VISAPIX feature in the ATSE component to enhance protection capabilities in Apex One (Mac) Security Agent.

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.