Sentinel 7.3 SP4 improves usability and resolves several previous issues.
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 on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ website 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 NetIQ Documentation page. To download this product, see the Sentinel Product Upgrade website.
For the latest version of this release notes, see Sentinel 7.3 Service Pack 4 Release Notes.
The following sections outline the key features and enhancements, and also the issues resolved in this release:
Sentinel 7.3 SP4 resolves a Java deserialization (CVE-2016-1000031) vulnerability. This security vulnerability (ZDI-16-570) was discovered by Jacob Baines from Tenable Network Security working with Trend Micro's Zero Day Initiative.
The following sections outline software issues resolved in this release:
For the list of software fixes and enhancements in previous releases, see the specific release notes.
Issue: When there is a long time gap between events sent to Sentinel by an event source, raw data files might get deleted. (Bug 999190)
Fix: Raw data files are no longer deleted even when there is a long time gap between events sent to Sentinel.
Issue: Enabling Sentinel server to run in FIPS 140-2 mode fails in RHEL if both 32-bit and 64-bit RPM packages are present in the server. (Bug 1000081)
Fix: The convert_to_fips.sh script now considers only the 64-bit RPM package.
For information about hardware requirements, supported operating systems, and browsers, see the Technical Information for Sentinel page.
You can upgrade to Sentinel 7.3 SP4 from Sentinel 7.0 or later.
Download the Sentinel installer from the NetIQ Download website. For information about upgrading to Sentinel 7.3 SP4, see Upgrading Sentinel
in the NetIQ Sentinel Installation and Configuration Guide.
If you are upgrading Sentinel 7.3 and later, the Change Guardian RPM is not upgraded by default. Therefore, the latest software fixes related to Change Guardian integration are not available. However, integration with Change Guardian works fine post upgrade. You can update the RPM manually. (BUG 953909)
To manually update the Change Guardian RPM:
Log in as the root user and go to the directory where the Sentinel installer is located.
Run the following command to check the Change Guardian RPM version bundled in Sentinel:
rpm -qa | grep ncgOverlay
Run the following command:
rpm -Uvh ncgOverlay-4.1.1.2-1104.i586.rpm
Run the following command to check whether the upgrade is successful:
rpm -qa | grep ncgOverlay
The output of this command should display the RPM version as 4.1.1.2.
(Conditional) If you are upgrading to Sentinel 7.3 SP4 from Sentinel 7.2 SP2 or older version, perform the following actions:
After the upgrade, the Search Proxy User role will not have the Allow users to manage alerts permission. This permission is necessary for the role to perform remote alert search. Assign the Allow users to manage alerts permission to the Search Proxy User role manually.
For more information, see Configuring Roles and Users
in the NetIQ Sentinel Administration Guide.
For consistency with newer versions of Sentinel and Sentinel documentation, rename the Search Proxy User role to Data Proxy User after the upgrade.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
The Java 8 update and the security vulnerability fixes included in Sentinel 7.3 SP1 might impact the following plug-ins:
Cisco SDEE Connector
SAP Connector
Remedy Integrator
For any issues with these plug-ins, NetIQ will prioritize and fix the issues according to standard defect-handling policies. For more information about support polices, see Support Policies.
Section 4.2, Cannot View Alerts with IPv6 Data in Alert Views
Section 4.8, Bar Mitzvah Security Vulnerability in Sentinel Link Connector
Section 4.10, Sentinel Agent Manager Does Not Consider the RawDataTapFileSize Configuration
Section 4.12, Data Synchronization Fails While Synchronizing IPv6 Addresses in Human Readable Format
Section 4.13, Event Search Does Not Respond if You Do Not Have Any Event Viewing Permissions
Section 4.18, New Incoming Alerts Incorrectly Appear to be Selected When You Modify Existing Alerts
Section 4.19, Loading Historical Security Intelligence Data Takes a Long Time
Section 4.25, Sentinel Does Not Configure the Sentinel Appliance Network Interface By Default
Section 4.26, The Web Browser Displays an Error When Exporting Search Results in Sentinel
Section 4.27, Sentinel Services Might Not Start Automatically After the Installation
Section 4.28, Cannot Enable Kerberos Authentication in Sentinel Appliance Installations
Section 4.30, Restarting a Remote Collector Manager Causes Some Event Sources to Lose Connection
Section 4.31, Unable to View More Than One Report Result at a Time
Section 4.32, Agent Manager Requires SQL Authentication When FIPS 140-2 Mode is Enabled
Section 4.33, Sentinel High Availability Installation in FIPS 140-2 Mode Displays an Error
Section 4.34, Sentinel High Availability Installation in Non-FIPS 140-2 Mode Displays an Error
Section 4.35, Appliance Update From Versions Prior to Sentinel 7.2 Fails in WebYaST
Section 4.37, Sentinel Link Action Displays Incorrect Message
Section 4.38, Dashboard and Anomaly Definitions with Identical Names
Section 4.39, Active Search Jobs Duration and Accessed Columns Inaccuracies
Issue: The security vulnerability fixes included in Sentinel 7.3 SP1 involved changes to the communication mechanism for a secured connection. These changes are not compatible with Sentinel UNIX Agent 7.4. Therefore, Sentinel cannot receive events from Sentinel UNIX Agent 7.4. (BUG 953990)
Workaround: There is no workaround at this time. This issue will be resolved when a compatible version of Sentinel UNIX Agent is made available.
Issue: Sentinel alert views and alert dashboards do not display alerts that have IPv6 addresses in IP address fields. (BUG 924874)
Workaround: To view alerts with IPv6 addresses in Sentinel, perform the steps mentioned in NetIQ Knowledgebase Article 7016555.
Issue: Sentinel displays an error when you try to configure NFS as secondary storage location after you Sentinel appliance to version 7.3 SP1 and later. (BUG 934851)
Workaround: After upgrading the Sentinel appliance, restart the SLES operating system using the following command:
init 6
Issue: When you upgrade Sentinel and start the Sentinel server, you might see the following exception in the server log:
Invalid length of data object ......
(BUG 933640)
Workaround: Ignore the exception. There is no impact to Sentinel performance because of this exception.
Issue: Sentinel uses the Diffie-Hellman protocol to communicate with Secure Configuration Manager. As part of fixing the Logjam vulnerability, the certificate key size for the Diffie-Hellman protocol in Sentinel has been increased to 2048. However, Secure Configuration Manager uses the default certificate key size; that is, 1024. Because of this mismatch, Secure Configuration Manager can no longer communicate with Sentinel. (BUG 935987)
Workaround: Until a fix is available from Secure Configuration Manager, you can perform the following steps:
WARNING:Performing this workaround overrides the fix for the Logjam vulnerability specified in Security Vulnerability Fixes
in the Sentinel 7.3.1 Release Notes.
Log in as the novell user and open the /etc/opt/novell/sentinel/config/configuration.properties file.
Comment out the following line following line by prefixing #:
jdk.tls.ephemeralDHKeySize=2048
Restart Sentinel.
Issue: As part of fixing the Bar Mitzvah vulnerability, Sentinel disabled the RC4 ciphers on SSL ports enabled for the Web server. However, Change Guardian uses RC4 ciphers to communicate with Sentinel. Therefore, Change Guardian can no longer communicate with Sentinel. (BUG 935401)
Workaround: Until a fix is available from Change Guardian, you can perform the following steps:
WARNING:Performing this workaround overrides the fix for the Bar Mitzvah vulnerability specified in Security Vulnerability Fixes
in the Sentinel 7.3.1 Release Notes.
Log in as the novell user and open the /etc/opt/novell/sentinel/3rdparty/jetty/jetty-ssl.xml file.
Delete the following lines from the ExcludeCipherSuites list:
<Item>SSL_RSA_WITH_RC4_128_SHA</Item>
<Item>SSL_RSA_WITH_RC4_128_MD5</Item>
Restart Sentinel.
Restart the Change Guardian service in the Change Guardian agent computer.
Issue: When Sentinel is integrated with Change Guardian 4.1, it does not display Change Guardian delta attached information, in spite of being configured to receive Change Guardian events. (BUG 936704)
Workaround: Upgrade Change Guardian to version 4.1.1 or later.
Or
The Change Guardian Solution Pack 2011.1r4 resolves this issue. Until it is officially released, you can download the Solution Pack from the Sentinel Plug-ins Previews website. You can view the delta information in the following Change Guardian reports after you apply the Solution Pack:
Change Guardian Events
Change Guardian Events by Asset
Change Guardian Events by Policy
Change Guardian Events by User
Issue: The Bar Mitzvah security vulnerability exists in Sentinel Link Connector. Sentinel Link Connector uses the RC4 algorithm in SSL and TSL protocols, which might allow plaintext recovery attacks against the initial bytes of a stream. For more information, see CVE-2015-2808. (BUG 933741)
Workaround: The Sentinel Link Connector version 2011.1r4 and later resolve this issue. Until it is officially released on the Sentinel Plug-ins website, you can download the Connector from the Previews section.
Issue: The Agent Manager Connector version 2011.1r3 does not set the CONNECTION_MODE property in the events if the Collector parsing the events supports multiple connection modes. (BUG 880564)
Workaround: The Agent Manager Connector version 2011.1r5 and later resolve this issue. Until it is officially released on the Sentinel Plug-ins website, you can download the Connector from the Previews section.
Issue: Sentinel Agent Manager ignores the value specified in RawDataTapFileSize attribute in the SMServiceHost.exe.config file for the raw data file size configuration, and stops writing to the raw data file when the file size reaches 10 MB. (BUG 867954)
Workaround: Manually copy the content of the raw data file into another file and clear it when the file size reaches 10 MB, so that Sentinel Agent Manager can write new data into it.
Issue: In upgraded installations of Sentinel 7.3, when you search for alert attributes in the Tips table in the Web interface, the search does not return the complete list of alert fields. However, alert fields display correctly in the Tips table if you clear the search. (BUG 914755)
Workaround: There is no workaround at this time.
Issue:
Data synchronization fails when you try to synchronize IPv6 address fields in a human readable format to external databases. For information about configuring Sentinel to populate the IP address fields in human readable dot notation format, see Creating a Data Synchronization Policy
in the NetIQ Sentinel Administration Guide. (BUG 913014)
Workaround: To fix this issue, manually change the maximum size of the IP address fields to at least 46 characters in the target database, and re-synchronize the database.
Issue: If run an event search when your role's security filter is blank and your role does not have event viewing permissions, the search does not complete. The search does not display any error message about the invalid event viewing permissions. (BUG 908666)
Workaround: Update the role with one of the following options:
Specify a criteria in the Only events matching the criteria field. If users in the role should not see any events, you can enter NOT sev:[0 TO 5].
Select View system events.
Select View all event data (including raw data and NetFlow data).
Issue: When editing a saved search upgraded from Sentinel 7.2 to a later version, the Event fields panel, used to specify output fields in the search report CSV, is missing in the schedule page. (BUG 900293)
Workaround: After upgrading Sentinel, recreate and reschedule the search to view the Event fields panel in the schedule page.
Issue: Sentinel does not return any correlated events when you search for all correlated events that were generated after the rule was deployed or enabled, by clicking the icon next to Fire count in the Activity statistics panel in the Correlation Summary page for the rule. (BUG 912820)
Workaround: Change the value in the From field in the Event Search page to a time earlier than the populated time in the field and click Search again.
Issue: Sentinel running in FIPS 140-2 mode does not display Change Guardian delta attached information when you search for Change Guardian events and click the Change Guardian icon, in spite of being configured to receive Change Guardian events. Change Guardian releases prior to version 4.2 do not support sending events in FIPS 140-2-compatible mode. (BUG 912230)
Workaround: There is no workaround at this time.
Issue: Upgrading to Sentinel 7.3 causes data collection and data synchronization with the DB2 database to fail, because the upgrade removes the IBM DB2 JDBC driver. (BUG 909343)
Workaround: After upgrading to Sentinel 7.3, add the correct JDBC Driver and configure it for data collection and data synchronization, by performing the following steps:
Copy the correct version of the IBM DB2 JDBC driver (db2jcc-*.jar) for your version of the DB2 database in the /opt/novell/sentinel/lib folder.
Ensure that you set the necessary ownership and permissions for the driver file.
Configure this driver for data collection. For more information, see the Database Connector documentation.
Issue: When you click Select All in alerts views to select alerts, deselect few alerts, and modify them, new incoming alerts are also selected in the refreshed alert views. This results in wrong count of alerts selected for modification, and also it appears as if you are modifying new incoming alerts too. However, only the originally selected alerts are modified. (BUG 904830)
Workaround: No new alerts will appear in the alert view if you create the alert view with a custom time range.
Issue: Historical Security Intelligence (SI) data takes a long time to load in Sentinel systems that have a high Events Per Second (EPS) load. (BUG 908599)
Workaround: If you are creating a security intelligence dashboard with historical data, plan to deploy the dashboard when the load on your system is lower, if possible. There is no other workaround at this time.
Issue: During Security Intelligence baseline regeneration, the start and finish dates for the baseline are incorrect and display 1/1/1970. (BUG 912009)
Workaround: The correct dates are updated after the baseline regeneration is complete.
Issue: Sentinel server shuts down when you run a search if there are a large number of events indexed in a single partition. (BUG 913599)
Workaround: Create retention policies in such a way that there are at least two partitions open in a day. Having more than one partition open helps reduce the number of events indexed in partitions.
You can create retention policies that filter events based on the estzhour field, which tracks the hour of the day. Therefore, you can create one retention policy with estzhour:[0 TO 11] as the filter and another retention policy with estzhour:[12 TO 23] as the filter.
For more information, see Configuring Data Retention Policies
in the NetIQ Sentinel Administration Guide.
Issue: Sentinel displays an error when you use the report_dev_setup.sh script to configure Sentinel ports for firewall exceptions. (BUG 914874)
Workaround: Configure Sentinel ports for firewall exceptions through the following steps:
Open the /etc/sysconfig/SuSEfirewall2 file.
Change the following line:
FW_SERVICES_EXT_TCP=" 443 8443 4984 22 61616 10013 289 1289 1468 1443 40000:41000 1290 1099 2000 1024 1590"
to
FW_SERVICES_EXT_TCP=" 443 8443 4984 22 61616 10013 289 1289 1468 1443 40000:41000 1290 1099 2000 1024 1590 5432"
Restart Sentinel.
Issue: Sentinel Generic Collector performance degrades when Generic Hostname Resolution Service Collector is enabled on Microsoft Active Directory and Windows Collector. EPS decreases by 50% when remote Collector Managers send events. (BUG 906715)
Workaround: There is no workaround at this time.
Issue: When you install Sentinel in FIPS 140-2 mode, connector to Security Intelligence database fails to start, and Sentinel cannot access Security Intelligence, Netflow, and alert data. (BUG 915241)
Workaround: Restart Sentinel after installing and configuring in FIPS 140-2 mode.
Issue: When installing Sentinel Appliance, the network interface is not configured by default. (BUG 867013)
Workaround: To configure the network Interface:
In the Network Configuration page, click Network Interfaces.
Select the network interface and click Edit.
Select Dynamic Address and then select either DHCP or Static assigned IP Address.
Click Next and then OK.
Issue: When exporting search results in Sentinel, the Web browser might display an error if you modify the operating system language settings. (BUG 834874)
Workaround: To export search results properly, perform either of the following:
While exporting the search results, remove any special characters (outside the ASCII characters) from the export filename.
Enable UTF-8 in the operating system language settings, restart the machine, and then restart the Sentinel server.
Issue: On systems with more than 2 TB disk space, Sentinel might not start automatically after the installation. (BUG 846296)
Workaround: As a one-time activity, start the Sentinel services manually by specifying the following command:
rcsentinel start
Issue: In Sentinel appliance installations, if you configure Kerberos authentication in the Kerberos module, the console displays a confirmation message that the Kerberos client configuration was successful. When you view the Kerberos module again, however, the Enable Kerberos Authentication option is deselected. (BUG 843623)
Workaround: There is no workaround at this time.
Issue: When you install a remote Collector Manager, if you specify a password that contains special characters, such as ‘$’, ‘"‘, ‘\’, or ‘/’, the installation fails with errors. (BUG 812111)
Workaround: Do not use special characters in the remote Collector Manager password.
Issue: When you restart a remote Collector Manager appliance, the Syslog event sources connected on the UDP port lose connection. (BUG 795057)
Workaround: There is no workaround available at this time.
Issue: While you wait for one report result PDF to open, particularly report results of 1 million events, if you click another report result PDF to view, the report result is not displayed. (BUG 804683)
Workaround: Click the second report result PDF again to view the report result.
Issue: When FIPS 140-2 mode is enabled in your Sentinel environment, using Windows authentication for Agent Manager causes synchronization with the Agent Manager database to fail. (BUG 814452)
Workaround: Use SQL authentication for Agent Manager when FIPS 140-2 mode is enabled in your Sentinel environment.
Issue: If FIPS 140-2 mode is enabled, the Sentinel High Availability installation displays the following error:
Sentinel server configuration.properties file is not correct. Check the configuration file and then run the convert_to_fips.sh script again to enable FIPS mode in Sentinel server.
However, the installation completes successfully. (BUG 817828)
Workaround: There is no fix or workaround available at this time. Although the installer displays the error, the Sentinel High Availability configuration works successfully in FIPS 140-2 mode.
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: There is no fix or workaround available at this time. Although the installer displays the error, the Sentinel High Availability configuration works successfully in non-FIPS 140-2 mode.
Issue: Appliance update from versions prior to Sentinel 7.2 fails because the vendor for the update packages has changed from Novell to NetIQ. (BUG 780969)
Workaround:
Use the zypper command to upgrade the appliance. For more information, see Upgrading the Appliance by Using zypper
in the NetIQ Sentinel Installation and Configuration Guide.
Issue: Solution Manager does not install correlation rules when a correlation rule with an identical name already exists on the system. A NullPointerException error is logged in the console. (BUG 713962)
Workaround: Ensure that all correlation rules have a unique name.
Issue: When you execute a Sentinel Link action from the Web interface Sentinel displays a success message even though the Sentinel Link Connector integrator test failed from the Sentinel Control Center. (BUG 710305)
Workaround: There is no workaround at this time.
Issue: When a Security Intelligence dashboard and an anomaly definition have identical names, the dashboard link is disabled on the Anomaly Details page. (BUG 715986)
Workaround: Ensure you use unique names when creating dashboards and anomaly definitions.
Issue: The Sentinel Web interface displays negative numbers in the Active Search Job Duration and Accessed columns when the Sentinel Web interface computer clock is behind the Sentinel server clock. For example, the Duration and Accessed columns display negative numbers when the Sentinel Web interface clock is set to 1:30 PM and the Sentinel server clock is set to 2:30 PM. (BUG 719875)
Workaround: Ensure the time on the computer you use to access the Sentinel Web interface is the same as or later than the time on the Sentinel server computer.
Issue: When you log in to the security dashboard and perform a search for IssueSAMLToken audit event, the IssueSAMLToken audit event displays incorrect hostname (InitiatorUserName) or (IP address) SourceIP. (BUG 870609)
Workaround: There is no workaround at this time.
Issue: Sentinel Control Center does not launch when the NetIQ Identity Manager Designer is installed on the client computer and Designer uses the system JRE. Designer needs to add some supporting jar files like xml-apis.jar to the lib/endorsed directory. Some of the classes in the xml-apis.jar file override the corresponding classes in the system JRE that is used by the Sentinel Control Center. (BUG 888085)
Workaround: Configure Designer to use its own JRE.
Issue: While collecting event data, Sentinel Agent Manager does not capture the Windows Insertion String fields with null values. (BUG 838825)
Workaround: There is no workaround at this time.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see http://www.netiq.com/company/legal/.
Copyright © 2016 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.