Release Notes

Abstract

This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar 7.5.0 Update Package 7 (7.5.0-QRADAR-QRSIEM-20230822112654) SFS. These instructions are intended for administrators who are upgrading to QRadar 7.5.0 Update Package 7 by using an SFS file.

Content

IMPORTANT: Administrators need to confirm their managed hosts are encrypted before you upgrade to QRadar 7.5.0 Update Package 7 to prevent a known issue with deploys documented as IJ49176/DT247083.

What's New

For more information on new and changed features in QRadar 7.5.0, see What's new in 7.5.0.

Read-only configuration
QRadar 7.5.0 Update Package 7 now has a new Read-only Configuration permission that grants users permission to view, but not create or edit, log sources or offenses. For more information, see Creating a user role.

Security change reminder for QRadar on Cloud

The SAASADMIN capability is now restricted to the Admin security profile. During the upgrade to QRadar 7.5.0 Update Package 7 any user or authorized service that has a User role with the SAASADMIN and a non-Admin security profile will be considered invalid and updated to the Disabled user role.

Security update - disabled cipher suites

To enhance the default security of your QRadar deployment, the following cipher suites are now disabled.

jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, DH keySize < 1024, DESede, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, DES_CBC, SHA1, CBC, SSL_RSA_WITH_AES_128_GCM_SHA256, SSL_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_AES_128_CBC_SHA256, SSL_RSA_WITH_AES_256_CBC_SHA256

Some older integrations could be impacted by this change.

Precheck added for postgresql11 migration

A precheck is added to check all hosts in your QRadar deployment to ensure that all hosts meet the free space requirements for postgresql 11 migration and upgrading. This precheck tests only to verify whether there is enough space to migrate the data and upgrade postgresql. If you launch the update package from your QRadar Console, the precheck checks all hosts in your deployment. Otherwise, it checks only the current host.

The postgresql 11 precheck is independent of the disk space requirements that are calculated by the update package. The update package determines the space required to upgrade the postgresql databases, as well as other RPMs and files needed for install/upgrade/copy.

Upgrading SOAR app might be required

If the IBM SOAR QRadar Plugin app is installed, you must upgrade to version 4.05 before you install QRadar 7.5.0 Update Package 7.

New certificate files to fix security browser warning

In QRadar 7.5.0 Update Package 7, vault has been replaced by QRadar certificate authority (CA) and intermediate CA. For more information, see Fixing the certificate security browser warning.

Adding QNI hosts to the Data Synchronization app

You can add QRadar Network Insight hosts to the QRadar® Data Synchronization app. For more information, see IBM QRadar Data Synchronization app.

Known Issues

After upgrading to QRadar 7.5.0 Update Package 5, WinCollect 7.X agents can experience management or configuration change errors

Important: A flash notice exists for this issue. For the latest information, see https://www.ibm.com/support/pages/node/6953887.

Autoupdates (AU) issue after upgrade to QRadar 7.5.0 or later
It is possible for autoupdates to revert to a previous version of autoupdates after upgrading. This causes autoupdate to not work as intended.

After you upgrade to QRadar 7.5.0 or later, type the following command to check your autoupdate version:

/opt/qradar/bin/UpdateConfs.pl -v

Review the issue and the resolution section for your auto update version on the following technical note, https://www.ibm.com/support/pages/node/6515880.

Docker services do not start when 7.2.8 or earlier appliances are updated to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3
Docker services fail to start on QRadar appliances that were originally installed at version 7.2.8 or earlier, then upgraded to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3.

Before you upgrade to QRadar 7.5.0 Update Package 2 Interim Fix 02 run the following command from the QRadar Console:

xfs_info /store | grep ftype

Review the output to confirm the ftype setting. If the output setting displays "ftype=0", do not proceed with the upgrade to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3.

For more information, see IJ41796.

Apps might go down during base image upgrade

After you install QRadar 7.5.0, your applications might go down temporarily while they are being upgraded to the latest base image.

Apps fail to restart after upgrade

After upgrading some apps remain in "error" state on deployments with 30+ apps. Restart the apps by using the qappmanager: /opt/qradar/support/qappmanager

For more information, see About the qappmanager support utility.

Issue adding Data Nodes to a cluster

When adding a Data Node to a cluster, they must either all be encrypted, or all be unencrypted. You cannot add both encrypted and unencrypted Data Nodes to the same cluster.

Kernel crash can affect UEFI systems in QRadar 7.4.0 Fix Pack 3 through to QRadar 7.4.3 Fix Pack 2.

If you are planning to upgrade from any version of QRadar 7.4.0 Fix Pack 3 through to QRadar 7.4.3 Fix Pack 2, contact support.

For more information, see IJ44385.

Hosts with EFI firmware and Secure Boot enabled may become unresponsive.
To avoid this problem, you must import the IBM public key contained on the SFS into the system keyring before patching. For more information, see Updating a Secure Boot enabled system.

STIG hardening box might break during system reboot

The STIG hardening box might break when the hardening script is run on certain systems and the system is rebooted. If you need to run a hardening script, complete the manual steps to boot password. If the system hits this defect, the system must be re-installed or reverted to recover it.

For more information, see IJ48710.

Resolved Issues

For a list of APAR links of resolved issues in QRadar 7.5.0 Update Package 7, see Authorized Program Analysis Reports.

Some APAR links might take 24 hours to display properly after a software release is posted to IBM Fix Central.

The following is a list of APARs fixed in QRadar 7.5.0 Update Package 7

IJ16414: Reports generate with incorrect chart data and column name with some advanced searches (AQL)
IJ29030: Log sources deleted from within log source groups can still appear in the QRadar user interface
IJ30347: "There was a problem saving the log source type configuration" after clicking save on the DSM editor page
IJ30863: QRadar content pack can cause offenses to be triggered off of source IP instead of custom event property configured in rule
IJ35845: Reports can be sent to user addresses in "multiple reports" option when "single report option" is selected
IJ35951: Benign error in patches.log file can be observed during or after a QRadar patch or upgrade
IJ36270: QRadar patching can fail due to disk space requirements when adequate space is available
IJ39393: Routing rule displays a blank page when the install is a software appliance on 7.5.0 UP1
IJ39620: Performance issues can occur when QRadar attempts a reload of sensor devices when log sources exceed 2 million
IJ39771: Scheduled weekly or monthly reports display "no data for chart" after upgrading to 7.5.0 UP5
IJ41206: App install fails during docker build with "an exception occurred while waiting for task to complete" error
IJ43426: Sorting by column in the offenses tab removes search filters
IJ43432: Tomcat might go out of memory during deployments when the user has millions of log sources
IJ43805: System notification displays incorrect message when the tomcat certificate is due to expire
IJ43957: Poor scalability in referencedata cache resulting in degrading search performance when using filters and tests
IJ44269: Users unable to export license information from QRadar console gui
IJ44724: QRadar asset creation events can display a generic identity:0 in the created by field for asset profiler events
IJ44868: Upgrade can complete and display an error about a custompropertiesscript trying to insert or update a table
IJ45396: Offense search can add unexpected filters to the current search parameters after closing an offense
IJ45679: Services can experience out of memory issues due to large certificate revocation lists (CLRS)
IJ45735: Reports tab can display as blank if the template file for a removed user is missing
IJ45829: Rule wizard cannot transition to the next page properly when rule response updates a reference table
IJ45914: QRadar system anomaly detection engine (ADE) rules can generate extra rules when modified multiple times
IJ45926: Anomaly rule enabling "test the [this accumulated property] value of each log source separately" displays application error
IJ46116: Offense summary for match count rules does not return all results for the event/flow count field
IJ46159: Rule tests with multiple reference set values can display "an error has occurred saving your rule"
IJ46184: QFlow collectors and processors in different domains can experience connection issues
IJ46231: Upgrading a detached app host appliance fails as the upgrade is waiting on docker and conman services
IJ46298: Standby HA appliances can run keystore certificate validator on inactive hosts causing benign log messages
IJ46916: Log activity tab can display event ID and category as N/A when the payloads are parsed and mapped correctly
IJ46986: Users cannot open the rules wizard from the offenses tab on QRadar 7.5.0 Update Package 6
IJ47011: Applications might fail to restart after apphost upgraded from UP5 to UP6
IJ47032: Unknown or stored events can route incorrectly to the sim generic log source in QRadar 750 UP4 and later
IJ47046: Reference data import fails with numberformatexception due to invalid number converter
IJ47049: Risks tab might not load after an upgrade to QRadar 7.5.0 UP6
IJ47129: Events can stop processing when pipelinediskmonitor detects the disk spillover threshold is crossed
IJ47194: Reports that use the "include date in email subject only" does not behave as expected
IJ47404: Ariel processes might not allocate enough memory for memory-heavy operations, causing slower searches
IJ47468: Advanced searches (AQL) that use the "in" operator do not use indexes as expected
IJ47587: Rule wizard for ADE rules does not preserve the state of the "test separately" check box
IJ47623: Completing a pretest with the installer -T command can cause Network Insights forensics issues
IJ47894: Scheduled daily reports do not generate on a weekend as expected
IJ45775: QRadar cannot log in while the LDAP server is unresponsive, which can lead to tomcat errors
IJ46702: PCAP data not stored in Ariel or displayed after an upgrade to QRadar 7.5.0 Update Package 2 or later
IJ46928: QRadar applications can get stuck in an error state after an upgrade to 7.5.0 Update Package 6
IJ24182: The tzdata DST rules for America/Santiago are out of date and have the incorrect date for switchover to DST.
IJ48422: QFlow services can experience service start or restart issues due to libpcap update for older avx2 processors.
IJ48423: User management window does not display as expected from the Admin tab when the language preference is non-English

Upgrade information

QRadar 7.5.0 Update Package 7 resolves reported issues from users and administrators from previous QRadar versions. This cumulative software update fixes known software issues in your QRadar deployment. QRadar software updates are installed by using an SFS file, and update all appliances attached to the QRadar Console.

The 750-QRADAR-QRSIEM-2021.6.6.20230519190832 SFS file can upgrade the following QRadar versions to QRadar 7.5.0 Update Package 7:

QRadar 7.3.2 (All versions from Fix Pack 3 to Fix Pack 7)
QRadar 7.3.3 (All versions from GA to Fix Pack 10)
QRadar 7.4.0 (All versions from GA to Fix Pack 4)
QRadar 7.4.1 (All versions from GA to Fix Pack 2)
QRadar 7.4.2 (All versions from GA to Fix Pack 3)
QRadar 7.4.3 (All versions from GA to Fix Pack 9)
QRadar 7.5.0 (All versions before Update Package 7)

However, this document does not cover all of the installation messages and requirements, such as changes to appliance memory requirements or browser requirements for QRadar. To review any additional requirements, see the QRadar Upgrade Guide.

See QRadar: Software update check list for administrators for a list of steps to review before you update your QRadar deployment.

Before you begin

Ensure that you take the following precautions:

Back up your data before you begin any software upgrade. For more information about backup and recovery, see the QRadar Administration Guide.
To avoid access errors in your log file, close all open QRadar sessions.
The QRadar software update cannot be installed on a managed host that is at a different software version from the Console. All appliances in the deployment must be at the same software revision to update the entire deployment.
Verify that all changes are deployed on your appliances. The update cannot install on appliances that have changes that are not deployed.
If this is a new installation, review the instructions in the QRadar Installation Guide.

Installing the QRadar 7.5.0 Update Package 7 Software Update

These instructions guide you through the process of upgrading an existing QRadar version to QRadar 7.5.0 Update Package 7. To update appliances in parallel, see: QRadar: How to Update Appliances in Parallel.

Procedure

Download the software update to install QRadar 7.5.0 Update Package 7 from the IBM Fix Central website: https://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+SIEM&release=All&platform=All&function=fixId&fixids=7.5.0-QRADAR-QRSIEM-20230822112654&includeSupersedes=0&source=fc
Use SSH to log in to your Console as the root user.
To verify you have enough space (5GB) in /store/tmp for the QRadar Console, type the following command:
```
  df -h /tmp /storetmp /store/transient | tee diskchecks.txt
```
- Best directory option: /storetmp
  It is available on all appliance types at all versions. In QRadar 7.5.0 versions /store/tmp is a symlink to the /storetmp partition.

If the disk check command fails, retype the quotation marks from your terminal, then rerun the command. This command returns the details to both the command window and to a file on the Console named diskchecks.txt. Review this file to ensure that all appliances have at minimum 5GB of space available in a directory to copy the SFS before attempting to move the file to a managed host. If required, free up disk space on any host that fails to have less that 5GB available.

Note: In QRadar 7.3.0 and later, an update to directory structure for STIG-compliant directories reduces the size of several partitions. This can impact moving large files to QRadar.

To create the /media/updates directory, type the following command:
```
  mkdir -p /media/updates
```
Use SCP to copy the files to the QRadar Console to the /storetmp directory or a location with 5GB of disk space.
Change to the directory where you copied the patch file. For example,
```
  cd /storetmp
```

To mount the patch file to the /media/updates directory, type the following command:

  mount -o loop -t squashfs /storetmp/7.5.0-QRADAR-QRSIEM-20230822112654.sfs /media/updates

To run the patch installer, type the following command:
```
  /media/updates/installer 
```
Note: The first time that you run the software update, there might be a delay before the software update installation menu is displayed.
Using the patch installer, select all.
- The all option updates the software on all appliances in the following order:
  1. Console
  2. No order required for remaining appliances. All remaining appliances can be updated in any order that you require.
- If you do not select the all option, you must select your Console appliance.
  
  As of QRadar 7.2.6 Patch 4 and later, you are only provided the option to update all or update the Console appliance. Managed hosts are not displayed in the installation menu to ensure that the Console is patched first. After the Console is patched, a list of managed hosts that can be updated is displayed in the installation menu. This change was made starting with QRadar 7.2.6 Patch 4 to ensure that the Console appliance is always updated before managed hosts to prevent upgrade issues.
  
  If you want to patch systems in series, you can update the Console first, then copy the patch to all other appliances and run the patch installer individually on each managed host. The Console must be patched before you can run the installer on managed hosts. When updating in parallel, there is no order required in how you update appliances after the Console is updated.
  
  If your Secure Shell (SSH) session is disconnected while the upgrade is in progress, the upgrade continues. When you reopen your SSH session and rerun the installer, the patch installation resumes.

Installation wrap-up

After the patch completes and you have exited the installer, type the following command:
```
  umount /media/updates
```
Clear your browser cache before you log in to the Console.
Delete the SFS file from all appliances.

Results

A summary of the software update installation advises you of any managed hosts that were not updated. If the software update fails to update a managed host, you can copy the software update to the host and run the installation locally.

After all hosts are updated, send an email to your team to inform them that they will need to clear their browser cache before they log in to the QRadar SIEM interface.

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtdAAA","label":"Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.5.0"}]

Tips

Release of QRadar 7.5.0 Update Package 7 SFS (7.5.0-QRADAR-QRSIEM-20230822112654)