12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.

0-QRADAR-QRSIEM-20230301133107)

Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-

QRSIEM-20230301133107)

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 5 (7.5.0-QRADAR-QRSIEM-20230301133107) SFS. These instructions
are intended for administrators who are upgrading to QRadar 7.5.0 Update Package 5 by using an SFS file.

Content

What's New
For information on new and changed features in QRadar 7.5.0, see What's new in 7.5.0
(https://www.ibm.com/docs/en/qsip/7.5?topic=750-qradar).

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 if 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 you have the IBM SOAR QRadar Plugin app installed, you must upgrade to version 4.05 before you install
QRadar 7.5.0 Update Package 5.

New certificate files to fix security browser warning

In QRadar 7.5.0 Update Package 5, vault has been replaced by QRadar Certificate Authority (CA) and
intermediate CA. For more information, see Fixing the certificate security browser warning
(https://www.ibm.com/docs/en/qsip/7.5?topic=problems-fixing-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
(https://www.ibm.com/docs/en/qradar-common?topic=apps-qradar-data-synchronization-app).

Known Issues
Important: QRadar 7.5.0 Update Package 5 contains tuning changes that can slow ecs-ec components
resulting in delays and events routing to storage as mentioned in IJ46418
(https://www.ibm.com/support/pages/apar/IJ46418). Administrators are advised to upgrade to QRadar 7.5.0
Update Package 5 Interim Fix 02
(https://www.ibm.com/support/fixcentral/swg/downloadFixes?parent=IBM%20Security&product=ibm/Other+software/IBM+Securit
y+QRadar+SIEM&release=All&platform=All&function=fixId&fixids=7.5.0-QRADAR-QRSIEM-20230503175608INT&includeRequis
ites=1&includeSupersedes=0&downloadMethod=http&source=fc)
to ensure they are not impacted.

Custom cache tuning overwritten during upgrades to QRadar 7.5.0 Update Package 5
https://www.ibm.com/support/pages/node/6959875 1/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)
Important: Upgrades to 7.5.0 Update Package 5 will overwrite custom cache tuning
in /opt/qradar/conf/spillovercache.properties. Before performing the upgrade, run the following command to
backup the file:

/opt/qradar/support/all_servers.sh -C cp -p /opt/qradar/conf/spillovercache.properties /root/spillovercahce.proper

It is possible the threshold values will need to be corrected after the upgrade is completed. Contact
support for further assistance.

Upgrades to QRadar 7.5.0 Update Package 5 might take longer to complete due to glusterfs file
cleanup
Important: Upgrades to QRadar 7.5.0 Update Package 5 might take an extended amount of time to
complete due to glusterfs file cleanup. You must allow the upgrade to continue uninterrupted.

For more information, see IJ45878 (https://www.ibm.com/support/pages/apar/IJ45878).

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 (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 will
cause 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 (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 (https://www.ibm.com/support/pages/apar/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.

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 (https://www.ibm.com/support/pages/apar/IJ44385).

https://www.ibm.com/support/pages/node/6959875 2/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

Resolved Issues
For a list of APAR links of resolved issues in QRadar 7.5.0 Update Package 5, see Authorized Program
Analysis Reports (https://www.ibm.com/community/qradar/support/apars/).

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 5

• IJ17793 (https://www.ibm.com/support/pages/apar/IJ17793): QRadar apps can stop running on an app host

after it is set up with High Availability (HA).

• IJ20449 (https://www.ibm.com/support/pages/apar/IJ20449): Geographic tests performed within QRadar can

cause performance issues due to XML parsing process.

• IJ21420 (https://www.ibm.com/support/pages/apar/IJ21420): QRadar dependency checker sometimes does

not find dependent rules or building blocks.

• IJ26159 (https://www.ibm.com/support/pages/apar/IJ26159): Restored config backups can cause an rpm

mismatch between the rpm version of dsm, protocols, vis, and the jars installed.

• IJ26662 (https://www.ibm.com/support/pages/apar/IJ26662): When overriding an eventID with two different

CEF or LEEF keys using the dsm editor/LSX, only the first is properly parsed.

• IJ29512 (https://www.ibm.com/support/pages/apar/IJ29512): The High Availability (HA) restore process

allows a primary to be rebuilt as a secondary 500 appliance.

• IJ29558 (https://www.ibm.com/support/pages/apar/IJ29558): The value of 'most recent results' in an offense

report displays as a negative when using a different user account.

• IJ29849 (https://www.ibm.com/support/pages/apar/IJ29849): Logging for tenant filtering only logs one tenant
and reports incorrect values.

• IJ30655 (https://www.ibm.com/support/pages/apar/IJ30655): 80xx log manager appliance type displays as

'event processor' in system and license management.

• IJ30904 (https://www.ibm.com/support/pages/apar/IJ30904): A managed host can fail to inherit the correct

license pool allocation when it has been re-added to a deployment.

• IJ31087 (https://www.ibm.com/support/pages/apar/IJ31087): Patching from a mounted sfs file in /store is

allowed by QRadar but can cause high availability patching to fail.

• IJ32804 (https://www.ibm.com/support/pages/apar/IJ32804): A non-admin user role user cannot re-assign or

move a log source to a different group using the log source management app.

• IJ32110 (https://www.ibm.com/support/pages/apar/IJ32110): The QRadar pipeline can stop receiving all

events due to a stringoutofboundsexception occurring.

• IJ32192 (https://www.ibm.com/support/pages/apar/IJ32192): Error written to QRadar logging: "There was an

error reading authentication.properties. Settings will not be reloaded".

• IJ32222 (https://www.ibm.com/support/pages/apar/IJ32222): Repetitive /var/log/audit.log messages being

written after a failed protocol test using the log source management app.

https://www.ibm.com/support/pages/node/6959875 3/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

• IJ32851 (https://www.ibm.com/support/pages/apar/IJ32851): Glusterfs migration or pretest can fail after

removing a 15xx appliance from the deployment.

• IJ33588 (https://www.ibm.com/support/pages/apar/IJ33588): Replication process can take longer than

expected on encrypted hosts after a high availability failover.

• IJ34833 (https://www.ibm.com/support/pages/apar/IJ34833): QRadar patching process to version 7.4.3 GA

and newer can fail while waiting on Tomcat service startup.

• IJ35115 (https://www.ibm.com/support/pages/apar/IJ35115): TaskManagementRetentionAgent can overload

Tomcat with threads causing it to fail.

• IJ35422 (https://www.ibm.com/support/pages/apar/IJ35422): Making a change on a high availability pair can

cause an unexpected active node reboot and failover.

• IJ35753 (https://www.ibm.com/support/pages/apar/IJ35753): QRadar is unable to verify SAML signatures in

some instances.

• IJ35972 (https://www.ibm.com/support/pages/apar/IJ35972): Null Pointer Exception occurs during log

source configuration where certificate key usage validation fails.

• IJ36280 (https://www.ibm.com/support/pages/apar/IJ36280): Event to identify indexed value is 'NULL' is not

generated by rules indexed by custom event properties.

• IJ36914 (https://www.ibm.com/support/pages/apar/IJ36914): Unable to delete QRadar user during

reassignment of custom flow properties.

• IJ36927 (https://www.ibm.com/support/pages/apar/IJ36927): 'Application error' can occur when disabling a

user that has dependencies.

• IJ39257 (https://www.ibm.com/support/pages/apar/IJ39257): Missing file /var/log/si-postgres-pam.log

causes some services to fail to properly startup.

• IJ39330 (https://www.ibm.com/support/pages/apar/IJ39330): Access to the user interface may be lost due to

missing authorized service tokens.

• IJ39414 (https://www.ibm.com/support/pages/apar/IJ39414): Event pipeline can stop due to

secstoreforwarddestinationjava.lang.interalerror:sigbus.

• IJ39771 (https://www.ibm.com/support/pages/apar/IJ39771): Scheduled reports can run on raw data causing

them to fail or take longer than expected to complete.

• IJ39773 (https://www.ibm.com/support/pages/apar/IJ39773): AQL equality operators do not work with AQL

xforce functions array output.

• IJ40009 (https://www.ibm.com/support/pages/apar/IJ40009): Users cannot access log source management

despite having manage log source and QRadar log source management permissions.

• IJ40290 (https://www.ibm.com/support/pages/apar/IJ40290): DSM parameter changes not being saved for

environment with single event collector.

• IJ40492 (https://www.ibm.com/support/pages/apar/IJ40492): AQL search with conditions imatches or ilike

return fewer results if the super index is used.

• IJ41078 (https://www.ibm.com/support/pages/apar/IJ41078): Upgrading a detached host or HA standby with

an expired license displays 'patch successful (with errors)'.

https://www.ibm.com/support/pages/node/6959875 4/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

• IJ41314 (https://www.ibm.com/support/pages/apar/IJ41314): Get_logs.sh does not run correctly on systems

that no longer support MegaCLI.

• IJ41598 (https://www.ibm.com/support/pages/apar/IJ41598): Geodata_update.sh returning false positive

notifications on HA standby consoles.

• IJ42235 (https://www.ibm.com/support/pages/apar/IJ42235): When running an AQL search with group by

using a cep value that exceeds 1000 characters, the cep value is truncated.

• IJ42297 (https://www.ibm.com/support/pages/apar/IJ42297): Modifying the rule 'multiple login failures for

single username' might cause an NPE error when QRadar is reading the rule.

• IJ43116 (https://www.ibm.com/support/pages/apar/IJ43116): Hostdefinition building block VA scanner source

IP is overwritten on every deploy if additional IP addresses are added.

• IJ43705 (https://www.ibm.com/support/pages/apar/IJ43705): QRadar.jsp call to

licensekeymanager.areLicensesValid() causes a delay on login for customers having multiple
managed hosts.

• IJ43767 (https://www.ibm.com/support/pages/apar/IJ43767): Users patching from QRadar 7.3.2 or 7.4.3 to

QRadar 7.5.0 might experience longer patch times than expected.

• IJ43769 (https://www.ibm.com/support/pages/apar/IJ43769): New searches started in the offenses tab

display incorrect time range options in the user interface.

• IJ44045 (https://www.ibm.com/support/pages/apar/IJ44045): An application error occurs when a domain

user attempts to assign an inactive offense.

• IJ44064 (https://www.ibm.com/support/pages/apar/IJ44064): Authenticated HTTP request failure response

incorrectly redirect win collect configuration requests to the login page.

• IJ44135 (https://www.ibm.com/support/pages/apar/IJ44135): Users who log in to QRadar can receive an

error 'invalid license key' when the license is valid.

• IJ44257 (https://www.ibm.com/support/pages/apar/IJ44257): Reference data API source response does not

reflect the requested API source value.

• IJ44273 (https://www.ibm.com/support/pages/apar/IJ44273) Application upgrades can fail when a health

check executes on all applications.

• IJ44418 (https://www.ibm.com/support/pages/apar/IJ44418): System rule names that were modified have

old name in offense summary.

• IJ44481 (https://www.ibm.com/support/pages/apar/IJ44481): Use Case Manager exports fail while session

was in an open transaction state.

• IJ44516 (https://www.ibm.com/support/pages/apar/IJ44516): Offense takes the offense start time from an

older unrelated partial match event.

• IJ44535 (https://www.ibm.com/support/pages/apar/IJ44535): Applications might fail to install because the

application start time exceeds 500 seconds.

• IJ44598 (https://www.ibm.com/support/pages/apar/IJ44598): QRM device backup failures caused by

spillover cache.

• IJ44708 (https://www.ibm.com/support/pages/apar/IJ44708): Domain mapped events might be incorrectly

tagged to the default domain.

https://www.ibm.com/support/pages/node/6959875 5/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

• IJ44709 (https://www.ibm.com/support/pages/apar/IJ44709): In QRadar, when IP addresses overlap during

deployment, known hosts values can be removed.

• IJ45041 (https://www.ibm.com/support/pages/apar/IJ45041): Authentication module settings page might be

blank in QRadar 7.5.0 UP4.

• IJ45191 (https://www.ibm.com/support/pages/apar/IJ45191): Offense summary page event/flow count field

does not match the event count in log activity.

• IJ45281 (https://www.ibm.com/support/pages/apar/IJ45281): Saving an LDAP repository can result in a

nullpointerexception error causing login.conf file to go blank.

• IJ45382 (https://www.ibm.com/support/pages/apar/IJ45382): Rules action for severity, credibility, and

relevance are not properly displayed in the UI after an update.

Security issues fixed in QRadar 7.5.0 Update Package 5.

• IBM QRadar SIEM is vulnerable to privilege escalation (CVE-2022-43863), see Security Bulletin
(https://www.ibm.com/support/pages/node/6964862).

• IBM QRadar SIEM is vulnerable to using components with known vulnerabilities, see Security
Bulletin (https://www.ibm.com/support/pages/node/6967016).

Upgrade information
QRadar 7.5.0 Update Package 5 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.5.20230301133107 SFS file can upgrade the following QRadar

versions to QRadar 7.5.0 Update Package 5:

• QRadar 7.3.2 (All versions from Fix Pack 3 to Fix Pack)

• 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 prior to Update Package 5)

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
(https://www.ibm.com/docs/en/SS42VS_7.5/pdf/b_qradar_upgrade.pdf).

See QRadar: Software update check list for administrators

(https://www.ibm.com/support/pages/qradar-software-update-checklist-administrators) for a list of steps to review before
you update your QRadar deployment.

https://www.ibm.com/support/pages/node/6959875 6/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

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
(https://www.ibm.com/docs/en/SS42VS_7.5/pdf/b_qradar_admin_guide.pdf).

• 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
(https://www.ibm.com/docs/en/SS42VS_7.5/pdf/b_siem_inst.pdf).

(install) Installing the QRadar 7.5.0 Update Package 5 Software Update

These instructions guide you through the process of upgrading an existing QRadar version to QRadar
7.5.0 Update Package 5. To update appliances in parallel, see: QRadar: How to Update Appliances in
Parallel (https://www.ibm.com/support/docview.wss?uid=swg21998517).

Procedure
1. Download the software update to install QRadar 7.5.0 Update Package 5 from the IBM Fix
Central website:
http://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-
20230301133107&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=fc
(http://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Secu

rity+QRadar+SIEM&release=All&platform=All&function=fixId&fixids=7.5.0-QRADAR-QRSIEM-20230301133107&include

Requisites=1&includeSupersedes=0&downloadMethod=http&source=fc)

2. Use SSH to log in to your Console as the root user.

3. 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 re-run 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.

https://www.ibm.com/support/pages/node/6959875 7/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

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.

1. To create the /media/updates directory, type the following command:

mkdir -p /media/updates

2. Use SCP to copy the files to the QRadar Console to the /storetmp directory or a location with
5GB of disk space.

3. Change to the directory where you copied the patch file. For example,
cd /storetmp

4. 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.5.20230301133107.sfs /media/up

5. 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.

6. 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

https://www.ibm.com/support/pages/node/6959875 8/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

1. After the patch completes and you have exited the installer, type the following command:
umount /media/updates

2. Clear your browser cache before you log in to the Console.

3. 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.

 Discover support videos on the IBM Helps

IBM Helps YouTube Subscribe to IBM Helps
channel.

Where do I find more information?

 QRadar 101

 QRadar Documentation

 IBM Helps Support Videos

 QRadar Support Forum

 QRadar Training

Document Information
More support for:
IBM Security QRadar SIEM (https://www.ibm.com/mysupport/s/topic/0TO5000000025xMGAQ)

Component:
QRadar Apps

Software version:
7.5.0

Operating system(s):
Linux

Document number:
6959875

https://www.ibm.com/support/pages/node/6959875 9/10
12/08/2024, 19:42 Release of QRadar 7.5.0 Update Package 5 SFS (7.5.0-QRADAR-QRSIEM-20230301133107)

Modified date:
12 May 2023

https://www.ibm.com/support/pages/node/6959875 10/10