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 Interim Fix 06 SFS. These instructions are intended for administrators who are upgrading to QRadar 7.5.0 Update Package 7 Interim Fix 06 by using an SFS file.
If IBM Fix Central displays an earlier interim fix version, you are not required to install earlier SFS interim fixes as QRadar 7.5.0 Update Package 7 Interim Fix 06 includes all software updates from prior interim fixes.
Content
What's New
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
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.
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.
Known Issues
To resolve this issue, complete the following steps:
- To add -Dcom.ibm.fips.silentUsage=true to the default Java options, run the following commands:
sed -i -e '$a\' /opt/ibm/java-x86_64-80/jre/lib/amd64/compressedrefs/options.default
echo "-Dcom.ibm.fips.silentUsage=true" >> /opt/ibm/java-x86_64-80/jre/lib/amd64/compressedrefs/options.default
- To remove the extra output from the store files that is used by the Apps, run the following command:
for dir in /etc/conman/secret/conman/containers/apps/*; do for storeDir in ${dir}/*/*; do if [ -f "${storeDir}/store" ] ; then echo "Fixing ${storeDir}/store"; sed -i '/FIPS/d' ${storeDir}/store; if ! cat "${storeDir}/store" | java -jar /opt/qradar/jars/ibm-si-mks.jar decrypt_command_line &>/dev/null; then echo "UPDATE FAILED for ${storeDir}/store"; fi fi done done
- To restart the App containers, run the following command:
systemctl restart container@*
An issue is identified where changes for managed WinCollect agents on 7.3.1 Patch 2 (7.3.1-28) do not complete as expected for encrypted managed hosts that attempt to connect to the Console on QRadar 7.5.0 Update Package 7 Interim Fix 5 and later. For more information about this known issue and details about a Console workaround, see DT269649.
It is possible for autoupdates to revert to a previous version of autoupdates after you upgrade. Older versions of autoupdate might not update RPMs as expected.
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
For more information, see IJ41796.
/opt/qradar/support/qappmanager
For more information, see IJ44385.
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.
Resolved Issues
Known Issues fixed in QRadar 7.5.0 Update Package 7 Interim Fix 06.
Upgrade information
QRadar 7.5.0 Update Package 7 Interim Fix 06 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 7.5.0-QRADAR-QRSIEM-20240225123426INT SFS file can upgrade the following QRadar versions to QRadar 7.5.0 Update Package 7 Interim Fix 06:
- QRadar 7.5.0 Update Package 7
- QRadar 7.5.0 Update Package 7 Interim Fix 01
- QRadar 7.5.0 Update Package 7 Interim Fix 02
- QRadar 7.5.0 Update Package 7 Interim Fix 03
- QRadar 7.5.0 Update Package 7 Interim Fix 04
- QRadar 7.5.0 Update Package 7 Interim Fix 05
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 you are attempting a new installation of QRadar, review the instructions in the QRadar Installation Guide.
Installing the QRadar 7.5.0 Update Package 7 Interim Fix 06 Software Update
These instructions guide you through the process of upgrading an existing QRadar version to QRadar 7.5.0 Update Package 7 Interim Fix 06. 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 Interim Fix 06 from the IBM Fix Central website: https://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+Vulnerability+Manager&release=All&platform=All&function=fixId&fixids=7.5.0-QRADAR-QRSIEM-20240225123426INT&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.
- Best directory option: /storetmp
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 you attempt 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 the directory structure for STIG-compliant directories reduces the size of several partitions. The reduced size can impact users who copy 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/750-QRADAR-QRSIEM-2021.6.7.20240225123426.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:
- Console
- 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 you update 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.
- The all option updates the software on all appliances in the following order:
Installation wrap-up
- After the patch completes and you exit 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.
Was this topic helpful?
Document Information
Modified date:
09 April 2024
UID
ibm17122752