IBM Support

Release of QRadar Incident Forensics 7.5.0 Update Package 8 Interim Fix 03 SFS (2021.6.8.20240527155707INT)

Release Notes


Abstract

This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar Incident Forensics 7.5.0 Update Package 8 Interim Fix 03 SFS. These instructions are intended for administrators who are upgrading to QRadar Incident Forensics 7.5.0 Update Package 8 Interim Fix 03 by using an SFS file.

Content

What's New

For more information on new and changed features in QRadar Incident Forensic 7.5.0, see What's new in 7.5.0.
 
Minimum Permitted App Base Image Stream
In QRadar 7.5.0 Update Package 8, you can disable older base image streams that might have security vulnerabilities by using the new Minimum Permitted App Base Image Stream system setting on the Admin tab. For more information, see Minimum Permitted App Base Image Stream.
 
Read-only Configuration
In QRadar 7.5.0 Update Package 8, the Read-only Configuration permission on the User Role Management window is updated to grant permission to view other users without the ability to create or edit them. For more information, see Creating a user role.
 
SSH extraction enhancements
In QRadar 7.5.0 Update Package 8, QRadar Network Insights introduces enhanced extraction for the SSH protocol. This functionality includes the extraction of several new fields around the SSH connection establishment and also the "Hash" fingerprints of those connections. For more information, see Enriched inspection.
 
Tunnelling enhancements
QRadar Network Insights introduces enhanced protocol support for GRE and ERSPAN network traffic and new common features for all tunneled network traffic (including the existing VXLAN support). For more information, see Enriched inspection.

Known Issues

Upgrade patch pretest fails on dual stack
After you upgrade to 7.5.0 Update Package 8, the RHEL-8 upgrade pretest fails after the system reboot.
 
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 you upgrade some apps remain in an "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.

Cannot send udp syslog to QRADAR_CONSOLE_IP from app container on an AppHost 
In QRadar 7.5.0 Update Package 8, you can not send Syslog UDP to QRADAR_CONSOLE_IP from app container on an AppHost.
 
Duplicate app entries on Traefik when QRadar console is powered off and on again
If you power off your QRadar console via VSphere and power it on again, duplicate entires of apps exist on the Traefik UI. To resolve this issue, restart the Traefik service. 
 
Factory reinstall on QRadar 7.5.0 Update Package 8 in the recovery partition fails on M5 hardware. 
Factory reinstall with Update Package 8 ISO in the recovery partition on M5 hardware is not supported. 
 
Alternatively, you can use one of the following methods:
For more information, see DT364088.
 
Managed WinCollect 7 agents cannot receive updates from encrypted QRadar Managed Hosts with 7.5.0 Update Package 8
In 7.5.0 Update Package 8 and later, administrators with managed WinCollect 7.x agents must update to 7.3.1 Patch 3 (7.3.1-43) to successfully receive updates from the Console. For more information, see DT269649.
Error messages appear during decapper startup in QRadar Network Insights
The following error messages on the terminal broadcast messages or decapper logs indicate an automatic fallback to a legacy decapper library on virtual hosts.
  
EAL: rte_mem_virt2phy(): cannot open /proc/self/pagemap: Permission denied

EAL: Cannot use IOVA as 'PA' since physical addresses are not available
This fallback is necessary when IOMMU and virtualization passthrough are not available and enabled in the virtual platform configuration. The decapper continues to function, possibly with lowered throughput.
 
Cert file /etc/httpd-qif/tls/httpd-qif.cert fails the key modulus check in QRadar 7.5.0 Update Package 8
After you upgrade your QRadar Incident Forensics Standalone (6100) appliance to 7.5.0 Update Package 8, cert file /etc/httpd-qif/tls/httpd-qif.cert fails the key modulus check. For more information, see DT365205.  
 
Admin password does not set correctly on auto-install
In some instances of QRadar installations using the auto-install method, the Admin password is not being set properly. To resolve this issues, manually update the Admin password in the QRadar host CLI. For more information, see DT258627.
 
HA pairing on QRadar console fails when Network File System (NFS) is configured on the QRadar 7.5.0 Update Package 8 install
To resolve this issue, add HA pairing before configuring NFS. For more information, see Configuring NFS backup on an existing HA cluster.

For more information, see DT364450.

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 you upgrade. Older versions of autoupdate might not update RPMs as expected.
 
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 in the following technical note, https://www.ibm.com/support/pages/node/6515880.
 
Issue adding Data Nodes to a cluster
When you add 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.

Resolved Issues

Known Issues fixed in QRadar Incident Forensics 7.5.0 Update Package 8 Interim Fix 03.

  • DT365799: Cannot send udp syslog to QRADAR_CONSOLE_IP from app container on Apphost.
  • DT386246: A kernel defect is causing a significant search performance degradation issue in QRadar 7.5.0 UP8 IF02.
  • DT365145:  HA synchronization status in 7.5.0 UP8 is not displayed in System and License Management.

Upgrade information

 

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

The 750-QRADAR-QRSIEM-2021.6.8.20240527155707 SFS file can upgrade the following QRadar Incident Forensic versions to QRadar Incident Forensic 7.5.0 Update Package 8 Interim Fix 03:

  • QRadar Incident Forensic 7.5.0 Update Package 8
  • QRadar Incident Forensic 7.5.0 Update Package 8 Interim Fix 01
  • QRadar Incident Forensic 7.5.0 Update Package 8 Interim Fix 02

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 Incident Forensic. 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 Incident Forensic 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 Incident Forensic 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 Incident Forensic 7.5.0 Update Package 8 Software Update

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

Procedure

  1. Download the software update to install QRadar Incident Forensic 7.5.0 Update Package 8 Interim Fix 03 from the IBM Fix Central website: https://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+Incident+Forensics&release=All&platform=All&function=fixId&fixids=7.5.0-QRADAR-QIFSFS-20240527155707INT&includeSupersedes=0&source=fc
  2. Use SSH to log in to your Console as the root user.
  3. To verify you have enough space (10 GB) 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 Incident Forensic 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 10 GB 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 10GB available.

  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 10GB 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/7.5.0-QRADAR-QIFSFS-2021.6.8.20240527155707.sfs /media/updates
  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 Incident Forensic 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 Incident Forensic 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.

Installation wrap-up

  1. After the system reboot is not initiated 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 Incident Forensic interface.

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"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"},{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSUK44","label":"IBM Security QRadar Incident Forensics"},"ARM Category":[{"code":"a8m0z000000cwtdAAA","label":"Upgrade"}],"Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.5.0"}]

Product Synonym

QRadar Incident Forensics

Document Information

Modified date:
27 June 2024

UID

ibm17155799

Page Feedback