This Hotfix resolves the following issue(s):
Users do not receive event notifications if the log generation time field is empty.
Solution
This hotfix ensures that Apex Central can send event notifications successfully when the log generation time field is empty.
Users cannot Single Sign-on (SSO) to Apex One from the Apex Central web console in debug mode.
Solution
This hotfix ensures that users can SSO to Apex One from the Apex Central web console in debug mode.
"msgHandlerRegistration.dll" may stop unexpectedly while recording output database connection errors to debug logs.
Solution
This hotfix ensures that "msgHandlerRegistration.dll" can record output database connection errors to debug logs normally.
Users cannot open the Apex Central web console on macOS Catalina because the Apex Central self-signed certificate does not comply with the new security requirements in iOS 13 and macOS 10.15.
Solution
To resolve this issue:
There are no issues for this Hotfix release.
There are no issues for this Hotfix release.
There are no enhancements for this Hotfix release.
There are no enhancements for this Hotfix release.
There are no enhancements for this Hotfix release.
Known issues in this release:
The file name of the attached ZIP file for a generated report contains garbled text if the report name contains non-alphanumeric characters.
The attached ZIP file for a generated report cannot be opened of the report name contains Traditional Chinese characters.
If Apex Central as a Service is the Node Apex Central of an on-premises Hub Apex Central server, Apex Central as a Service might not be able to receive Suspicious Object Lists from the on-premises Hub Apex Central.
To resolve this issue, contact your support representative.
Known issues in this release:
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.
Known issues in this release:
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.