Sentinel 8.4.0.1 resolves several previous issues and also adds a few new features.
Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Sentinel forum, our online community that also includes product information, blogs, and links to helpful resources. You can also share your ideas for improving the product in the Ideas Portal.
The documentation for this product is available in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click the comment icon on any page in the HTML version of the documentation posted at the Sentinel Documentation page. To download this product, see the Product Download website.
IMPORTANT:The Scalable Storage feature will be discontinued from the next version of Sentinel.
The following sections outline the key features provided by this version, as well as issues resolved in this release:
The Log4j vulnerability allows malicious attackers to execute code remotely on any targeted system.
Log4j vulnerabilities are addressed as follows:
A series of high severity vulnerabilities (CVE-2021-44228), (CVE-2021-45105), (CVE-2021-45046), and (CVE-2021-44832) for new Apache Log4j 2 version 2.8.2 are disclosed publicly and this has been addressed in this release by upgrading log4j to latest version 2.17.1
A series of high severity vulnerabilities (CVE-2021-4104) and (CVE-2019-17571) for older Apache log4j version log4j-1.2.17.jar are disclosed publicly and it has been mitigated by removing vulnerable classes.
The vulnerable class is removed from the Elasticsearch bundled log4j-core-2.11.1.jar used in Sentinel.
Sentinel 8.4.0.1 includes software fixes that resolve the following issues:
Issue: After upgrading Sentinel Java Client from 8.1 to 8.2, REST calls failing.
Fix: Now after upgrading Sentinel Java Client from 8.1 to 8.2, REST calls not failing.
For more information about hardware requirements, supported operating systems, and browsers, see the Sentinel System Requirements.
For information about installing Sentinel 8.4.0.1, see the Sentinel Installation and Configuration Guide.
NOTE:Fresh installation of 8.4.0.1 is only supported for traditional setup but not for appliance.
You can upgrade to Sentinel 8.4.0.1 from any prior versions of Sentinel (from Sentinel 8.2 and later).
IMPORTANT:Upgrading to Sentinel 8.4.0.1 is only supported in Traditional installation. For appliance, upgrade to 8.4.0.1 is not supported, however you can upgrade to Sentinel 8.5.0.1 either through channel update or using Offline Patch ISO.
IMPORTANT:Upgrading to Sentinel 8.5.0.0 from Sentinel 8.4.0.1 is not supported. However, you can upgrade to Sentinel 8.5.0.1
IMPORTANT:There is a change in the upgrade procedure of Traditional installation. Please refer to Settings in Elasticsearch for Secure Cluster Communication and follow the steps. This is only applicable if you are upgrading Sentinel to 8.4.0.1 version from 8.3.1.0 and prior.
WARNING:If you are upgrading from versions prior to Sentinel 8.3, you must manually assign the Send events and attachments permission to non-administrator users who send events or attachments to Sentinel. Unless you assign this permission, Sentinel will no longer receive events and attachments from Change Guardian and Secure Configuration Manager.
For Traditional installation, refer to Upgrading the Operating System section in Sentinel Installation and Configuration Guide.
Micro Focus strives to ensure our products provide quality solutions for your enterprise software needs. The following known issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
The Java 8 update included in Sentinel might impact the following plug-ins:
Cisco SDEE Connector
SAP (XAL) Connector
Remedy Integrator
For any issues with these plug-ins, we will prioritize and fix the issues according to standard defect-handling policies. For more information about support polices, see Support Policies.
Error When Launching a Kibana Dashboard After Upgrading Sentinel
Cannot Copy the Alert Links of All the Alerts in an Alert View in Mozilla Firefox and Microsoft Edge
Sentinel 8.2 Appliance in Microsoft Hyper-V Server 2016 Does Not Start When You Reboot
SSDM Displays an Exception When Deleting Events Whose Retention Period Has Expired
Collector Manager Runs Out of Memory if Time Synchronization is Enabled in Open-vm-tools
Agent Manager Requires SQL Authentication When FIPS 140-2 Mode is Enabled
Sentinel High Availability Installation in Non-FIPS 140-2 Mode Displays an Error
Sentinel Does Not Process Threat Intelligence Feeds In FIPS Mode
The Kibana Custom Dashboard is not Displayed After Upgrading to Sentinel 8.3.1
When you Launch Kibana the Conflict Error Message is Displayed
When you Reboot OS Redhat 8.1 and 8.2, Sentinel is not Started Automatically
When you Open Sentinel Appliance Management Console an Error Message is Displayed
When Admin Changes User Role of Alerts, Immediately Changes are not Updated in the Kibana Page
When you Launch the Visualization Dashboard as a Tenant User, an Error Message is Displayed
In RHEL, RCM and RCE are not Connecting to the Server When CRL is Enabled
Issue: In Sentinel Main > Storage > Health, the Storage Capacity Forecasting chart is not available. This is because Zulu OpenJDK does not include the necessary fonts. (Bug 1146879)
Workaround: Use the following commands to install the fonts:
yum install fontconfig
yum install dejavu
Issue: Launching a Kibana dashboard displays the following message: No default index pattern. You must select or create one to continue. (Bug 1163143)
Workaround: To set a Kibana index pattern as the default index pattern:
Select any of the following:
alerts.alerts
security.events.normalized_*
Click Set as Default.
Issue: The Select All <number of alerts> Alerts > Copy Alert Link option does not work in Firefox and Edge. (Bug 1162070)
Workaround: Perform the following steps:
Manually select all the alerts on each page of the alert view using the check box that allows you to select all the alerts.
Click Copy Alert Link.
Paste it in the desired application.
Issue: The installer halts at the installation in progress screen and does not display the login screen even though the installation is complete.
Workaround: Reboot the virtual machine and launch Sentinel, Collector Manager, or Correlation Engine. (Bug 1134657)
Issue: In Hyper-V Server 2016, Sentinel appliance does not start when you reboot it and displays the following message:
A start job is running for dev-disk-by\..
This issue occurs because the operating system modifies the disk UUID during installation. Therefore, during reboot it cannot find the disk.
(Bug 1097792)
Workaround: Manually modify the disk UUID. For more information, see Knowledge Base Article 7023143.
Issue: When you upgrade to Sentinel 8.2 HA appliance, Sentinel displays the following error:
Installation of novell-SentinelSI-db-8.2.0.0-<version> failed:
with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a):
(Bug 1099679)
Workaround: Before you respond to the above prompt, perform the following:
Start another session using PuTTY or similar software to the host where you are running the upgrade.
Add the following entry in the /etc/csync2/csync2.cfg file:
/etc/opt/novell/sentinel/config/configuration.properties
Remove the sentinel folder from /var/opt/novell:
rm -rf /var/opt/novell/sentinel
Return to the session where you had initiated the upgrade and enter r to proceed with the upgrade.
Issue: Installation of Collector Manager and Correlation Engine appliance fails in MFA mode if the operating system language is other than English. (Bug 1045967)
Workaround: Install Collector Manager and Correlation Engine appliances in English. After the installation is complete, change the language as needed.
Issue: The Next and Back buttons in the appliance installation screens do not appear or are disabled in some cases, such as the following:
When you click Back from the Sentinel precheck screen to edit or review the information in the Sentinel Server Appliance Network Settings screen, there is no Next button to proceed with the installation. The Configure button allows you to only edit the specified information.
If you have specified incorrect network settings, the Sentinel Precheck screen indicates that you cannot proceed with the installation due to incorrect network information. There is no Back button to go to the previous screen to modify the network settings.
(Bug 1089063)
Workaround: Restart the appliance installation.
Issue: Sentinel displays the following message during start up in the server.log file:
Value for attribute rv43 is too long
(Bug 1092937)
Workaround: Ignore the exception. Although the message is displayed, Sentinel works as expected.
Issue: When there is a large number of events whose retention period has expired and SSDM tries to delete those events from Elasticsearch, the following exception is displayed in the server.log file:
java.net.SocketTimeoutException: Read timed out
(Bug 1088511)
Workaround: Ignore the exception. This exception occurs due to the time taken to delete the large amount of data. Although the exception is displayed, SSDM successfully deletes the events from Elasticsearch.
Issue: If you manually install and enable time synchronization in open-vm-tools, they periodically synchronize time between the Sentinel appliance (guest) and the VMware ESX server (host). These time synchronizations can result in moving the guest clock either behind or ahead of the ESX server time. Until the time is synchronized between the Sentinel appliance (guest) and the ESX server (host), Sentinel does not process events. As a result, a large number of events are queued up in the Collector Manager, which may eventually drop events once it reaches its threshold. To avoid this issue, Sentinel disables time synchronization by default in the open-vm-tools version available in Sentinel. (Bug 1099341)
Workaround: Disable time synchronization. For more information about disabling time synchronization, see Disabling Time Synchronization.
Issue: When FIPS 140-2 mode is enabled in Sentinel, using Windows authentication for Agent Manager causes synchronization with the Agent Manager database to fail. (Bug 814452)
Workaround: Use SQL authentication for Agent Manager.
Issue: The Sentinel High Availability installation in non-FIPS 140-2 mode completes successfully but displays the following error twice:
/opt/novell/sentinel/setup/configure.sh: line 1045: [: too many arguments
(Bug 810764)
Workaround: The error is expected and you can safely ignore it. Although the installer displays the error, the Sentinel High Availability configuration works successfully in non-FIPS 140-2 mode.
Issue: While using Keytool command, the following warning is displayed:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12which is an industry standard format using "keytool -importkeystore -srckeystore /<sentinel_installation_path>/etc/opt/novell/sentinel/config/.webserverkeystore.jks -destkeystore /<sentinel_installation_path>/etc/opt/novell/sentinel/config/.webserverkeystore.jks -deststoretype pkcs12".
(Bug 1086612)
Workaround: The warning is expected and you can safely ignore it. Although the warning is displayed, Keytool command works as expected.
Issue: In FIPS mode, when processing out-of-the-box threat Intelligence feeds from URLs, Sentinel displays the following error: Received fatal alert: protocol_version. This issue occurs because the out-of-the-box threat feeds now support only TLS 1.2, which does not work in FIPS mode. (Bug 1086631)
Workaround: Perform the following:
Click Sentinel Main > Integration > Threat Intelligence Sources.
Edit each URL to change the protocol from http to https.
Issue: In multi-factor authentication mode, if you log out of Sentinel Main you do not get logged out of Sentinel dashboards and vice versa. This is due to an issue in the Advanced Authentication Framework. (Bug 1087856)
Workaround: Until a fix is available in the Advanced Authentication Framework, refresh the screen to view the login screen.
Issue: The Kibana custom dashboard is not displayed when you upgrade from Sentinel 8.3 or earlier to Sentinel 8.3.1.(Bug 58001)
Workaround: Ensure that you re-create the custom dashboard after upgrading Sentinel.
Issue: After installing or upgrading Sentinel and when you launch Kibana for the first time, the conflict error message is displayed.(Bug 65001)
Workaround: Ignore the conflict error message as there is no functionality impact.
Issue: After installing Sentinel on OS Redhat 8.1 and 8.2, Sentinel (Server, RCM, or RCE) is not started automatically after reboot.(Bug 83167)
Workaround: Change the SELINUX value to SELINUX=disabled in the file /etc/selinux/config.
Issue: After upgrading to Sentinel 8.3, when you try to open Sentinel Appliance Management Console of the CE (Correlation Engine) or CM (Collector Manager) of HA (High Availability) servers, an error message Error 404 - Not found is displayed. (Bug 93058)
Workaround: For more information, refer to Micro Focus Knowledge Base document.
Issue: After upgrading to Sentinel 8.4, users with hide management permission of visualization still can see the Management tab on the Kibana page, but cannot access the features of the Management tab. (Bug 112007)
Issue: Existing users unable to see any alerts on the Kibana page immediately, although permission is updated by the admin to see the alerts. (Bug 115010)
Workaround: You need to logout and login again when the user permission is updated.
Issue: When a non-default tenant user launches the visualization dashboard, an error message Forbidden is displayed. This error message is displayed, whenever the dashboard is launched by the non-default tenant user who has View-only permission for the Management option and there is no user with Edit permission for the Management option under that tenant.(Bug 112008)
Workaround: Ignore the error message as there is no functionality impact.
Issue: Remote Collector Manager (RCM) and Remote Correlation Engine (RCE) not able to connect to the server when CRL is enabled, in RHEL.(Bug 121001)
Workaround: Upgrade the cURL version on the machine to 7.60 or above.
Issue: In the fresh installation of distributed setup, after enabling the Event Visualization, the FIPS, and the CRL services, the Remote Collector Manager (RCM) is not forwarding the events to the Sentinel Server. (Bug 121002)
Workaround: If either the Event Visualization and FIPS or the Event Visualization and CRL are enabled, then RCM forwards the events to the Sentinel server.
Issue: When you are upgrading the Operating System, from an older version to the latest version, incident reports fail with exceptions. (Bug 115047)
For specific product issues, contact Micro Focus Support at https://www.microfocus.com/support-and-services/.
Additional technical information or advice is available from several sources:
Product documentation, Knowledge Base articles, and videos: https://www.microfocus.com/support-and-services/
The Micro Focus Community pages: https://www.microfocus.com/communities/
© Copyright 2001-2022 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
For additional information, such as certification-related notices and trademarks, see http://www.microfocus.com/about/legal/.