The banner on the "User-Defined Suspicious Objects" tab contains inaccurate information.

C&C Callback event notifications display an "unknown action" error when users attempt to use the "%act%" token variable.

Filtered policies cannot be deployed successfully to agents in subdomains that contain an apostrophe "'".

When Data Loss Prevention(TM) (DLP) logs are sent in syslog form, policy names appear as "N/A".

Device Control logs cannot be queried from the "Logs Query" page.

CSS style errors cause columns to overlap when printing pages.

It may take a long time to generate a report using a template that contains the "Endpoint Pattern/Engine Status Summary". When this happens, the report generation task remains in "In progress" status.

Users do not receive scheduled report notification email messages.

The wrong scan method information appears in the "Product View" page.

No results display when users run a Log Query and select the same date in the two date fields of the "Custom Range" date filter.

An issue prevents Apex Central from generating Active Directory user group reports successfully.

An issue prevents Apex Central from forwarding Intrusion Prevention logs to the syslog server.

An exception occurs when users click the "View" in the Security Threat Details table of the Threats tab.

Apex Central is unable to save SSO service URLs that contain special characters.

A Deploy Pattern Update command may be cancelled by the next Deploy Pattern update command even if the commands contain different components. As a result, some components are not deployed to the product server.

Users cannot import policies normally.

The Apex One Security Agent cannot retrieve the latest Application Control criteria because the Application Control policy content is incomplete.

An issue prevents users from selecting or deselecting applications in the Application Reputation List of the Application Control Criteria.

The Application Control certificate criteria does not work normally when matching by certificate types.

In certain rare condition, after enabling Endpoint Sensor, certain endpoints may encounter a hardware conflict resulting in a Blue Screen of Death (BSOD).

The Data Loss Prevention(TM) (DLP) feature may block the USB Scanner application unexpectedly.

Known vulnerability issue found in the help_start.php file.

This hotfix improves the product profile merge operation to reduce job failures.

This hotfix increases the maximum supported DLP file size from 2 GB to 1024 GB.

This hotfix applies the following changes to the Firewall Violations log:

• Renames the following columns:
  • "Endpoint IP" to "Destination IP"
  • "Endpoint Port" to "Destination Port"
  • "Target Application" to "Target Process"
• Adds the "Source Port" column

This hotfix updates the following error messages that display when iVP policy deployment fails.

Error Code 130 From: Vulnerability Protection Service: Policy deployment unsuccessful: Unable to uninstall incompatible agent program To: Vulnerability Protection Service: Unable to deploy. Deep Security installed

Error Code 112 From: Vulnerability Protection Service: Policy deployment unsuccessful: Incompatible agent program on endpoint To: Vulnerability Protection Service: Policy deployment unsuccessful: Unable to deploy. Deep Security installed

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

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.