IBM Support

Release of QRadar Incident Forensics 7.5.0 Update Package 11 SFS (2021.6.11.20250122185136)

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 11 SFS. These instructions are intended for administrators who are upgrading to QRadar Incident Forensics 7.5.0 Update Package 11 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.
Upgraded Red Hat Operating System from 8.8 to 8.10
In QRadar 7.5.0 Update Package 11, Red Hat Enterprise Linux is upgraded to version 8.10. For more information, see Red Hat Enterprise Linux 8.10.
 
Increased default UDP payload size Juniper ISO image to 2048 bytes
In QRadar 7.5.0 Update Package 11, the default UDP payload size for JSA (Juniper) ISO image is increased to 2048 bytes to reduce parsing issues for payloads exceeding 1024 bytes.
 
Default dashboard in Qradar is set to the Analyst Workflow App
In QRadar 7.5.0 Update Package 11, the default dashboard in QRadar is set to Analyst Workflow App (AWF), You can toggle between the AWF dashboard and legacy dashboards as needed. If AWF is not installed during the upgrade process or you uninstall it, the default dashboard reverts to the legacy dashboard. 
 
Improved JSON performance for offline forwarding of flows
The Flow Rate (FPS) is increased for offline forwarding with JSON type to improve performance.
 
Added support to create an asset by using the asset_model Rest API interface 
In QRadar 7.5.0 Update Package 11, you can create an asset by using the /api/asset_model Rest API interface. 
 
Added support to create a new log source group and log source type in the Log Source Management App
In QRadar 7.5.0 Update Package 11, you can now create log source groups directly in the Log Source Management App. You can also create a new log source type by using the DSM Editor button that is available on the Single Log Source and Multiple Log Source creation pages. 
 
Improved the installation process of OOTB apps
In QRadar 7.5.0 Update Package 11, you can directly install the latest version of Out-of-the-Box (OOTB) apps on the V4 minimum app base image stream. The older versions of the apps are skipped during installation if a higher or equal version of the app is already installed. 
 
Upgraded Apache Struts to the latest 6.x version
Apache Struts is upgraded to the latest 6.x version. This update improves support and response time for related security fixes and enhances compatibility with newer versions of Java. 
 
Added an offense API endpoint for OCSF 
You can now view the offense API output in the OCSF (Open Cybersecurity Schema Framework) format by using the new endpoint under siem/offense_ocsf.

Known Issues

Assets can not be updated or deleted
Due to an issue in the Postgres database, a duplicate asset is created when you attempt to update an asset that is created by OS discovery before the upgrade to Update Package 11. The original assets created by OS discovery and the duplicate assets can not be updated or deleted. For more information, see DT423580. 
 
QRadar 7.5.0 Update Package 11 Interim Fix 01 patch fails on appliance installs
The QRadar 7.5.0 Update Package 11 Interim Fix 01 patch hangs on appliance installs during the cliniq check on grub files, and the following message is displayed.
File not found: /etc/grub.d/00_tuned.
To resolve this issue, create an empty file named /etc/grub.d/00_tuned. For more information, see DT423724.
WinCollect 7.3.1-43 upgrade fails
The WinCollect RPM validation is out of date and causes the upgrade to fail. To resolve the issue, and for more information, see WinCollect 7.3.1-43 upgrade fails due to "[CRITICAL] Transaction failed.
Access to X-Force servers 
You can not access X-Force servers directly from a QRadar IPv6 box. To use X-Force in queries or custom rules, configure a proxy server. To enable a proxy, and for more information, see QRadar: X-Force Frequently Asked Questions.
 
Upgrading to QRadar 7.5.0 Update Package 8 or later from QRadar version 7.2.x can fail due to insufficient disk space
In QRadar version 7.3.0 or earlier, appliances were built with smaller partition sizes that can cause issues when you upgrade to RHEL-8. Depending on the appliance type, you can save the SFS file in a different directory or rebuild the system at Update Package 8 or later, and then add it to the deployment. 
 
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.
 
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. 
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. 
 
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.

Autoupdates (AU) issue after upgrade
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
For more information about the issue and the resolution for your auto update version, see technote 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


For a list of Known Issues links of resolved issues in QRadar Incident Forensic 7.5.0 Update Package 11, see Known Issues. The Known Issues search page allows users to search for Known Issues by version or status.

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

The following is a list of Known Issues fixed in QRadar Incident Forensic 7.5.0 Update Package 11:

  • DT421290: Test_tomcat_connection.sh fails during qchange_netsetup when hostname is changed in Console.
  • DT419580: Incorrect Japanese translation under user theme selection form/wizard.
  • DT418747: QRadar 7.5.0 UP10 running qchange_netsetup on a console will hang while committing changes.
  • DT400995: Tomcat/hostcontext will fail after patching to UP10 if ARIEL_FREE_TEXT_*_INDEX is set to yes.
  • DT419866: Inefficient synchronization in ReferenceDataCache causing a performance degradation in CRE, Parsing, Routing rules etc. 
  • DT398931: Offense tab consistently sorts offences in ascending order, regardless of the sorting order specified in the saved search.
  • DT398593: HA SelfRepair.sh script fails to run to repair ha when in a failed state.
  • DT398675: Patch fails on an MH with Tomcat enabled before the patch.
  • DT391513: AQL properties do not parse and report 'N/A' in Log Activity.
  • DT397036: TCP syslog log sources goes into an error state after a full deployment when changing the advanced setting 'Max Number of TCP Syslog Connections'. 
  • DT417402: Upgrade stuck with incorrect status report in Parallel patch menu.
  • DT396457: Event Start time shows "N/A" after upgrade.
  • DT392098: The REFERENCEMAPSETCONTAINS used in AQL does not respect ALNIC type of reference object.
  • DT244813: IJ48955 - Log File protocol configured to connect with SFTP can stop collecting events unexpectedly in 7.5.0 UP7.
  • DT395212: NPE when calling GEO::LOOKUP function.
  • DT394567: QRadar - Multiline log messages in Bandwidth Manager's qradar.log seen as stored events in log activity.
  • DT393769: Offense filter "Assigned to user is Unassigned" does not work in UP9.
  • DT396561: Viewing Events Associated With an Offense May Show Incomplete Results.
  • DT394013: Host address value is empty for online forwarded events.
  • DT391457: REFERENCEMAP functions do not return correct results in Log Activity when used twice in same expression with Group By.
  • DT390330: Error - No certificate was found with friendly name [friendly_name].
  • DT381380: Quick Filter doesn't auto-update results after filter change/removal.
  • DT393659: Qradar appliance installation fails on systems with Secure Boot enabled.
  • DT381852: Search results in application error if the special characters in filters exceed the 255 handle_name limit.
  • DT378765: JSON CEPs handle backslashes as escapes.
  • DT378773: Sentry Engine doesn't reflect data from all hosts.
  • DT378759: Deleting a domain can cause Reference Set element count in the UI to report incorrectly.
  • DT258972: Search results aren't removed from /transient when the cursor has a ' . '.
  • DT392621: Cisco unknown events are incorrectly mapped in the DSM Editor to another known event %ASA-7-718088.
  • DT252114: IJ49400 - Alphanumeric ignore case (ALNIC) data type does not work for reference table keys.
  • DT256896: SourceMonitor Reporting incorrect high EPS rates for time windows over 5 seconds.
  • DT252077: IJ47012 - ADE rules created from searches using a reference set filter causes socket leak in the accumulator. 
  • DT394515: Can not Delete a Group in Group-Based LDAP.
  • DT252032: IJ44962 - Ariel restart slows down because searches order by date format creates garbage folders in /store/transient/ariel_proxy_server/data.
  • DT149096: IJ42377 - Ariel.dataloader may cause a Nullpointerexception error while fetching the name of the sensor device type for ID 0. 
  • DT108131: IJ33756 - QRadar user interface may become unavailable when navigating in the extension management window. 
  • DT251744: IJ32428 - Unable to delete saved searches. 
  • DT420540: UCM 4.0.0 crashes when a user tries to add or edit an MITRE mapping.
     

Upgrade information


QRadar Incident Forensic 7.5.0 Update Package 11 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.11.20250122185136 SFS file can upgrade the following QRadar Incident Forensic versions to QRadar Incident Forensic 7.5.0 Update Package 11:

  • QRadar Incident Forensic 7.5.0 Update Package 8
  • QRadar Incident Forensic 7.5.0 Update Package 8 Interim Fix 01 to Interim Fix 03
  • QRadar Incident Forensic 7.5.0 Update Package 9
  • QRadar Incident Forensic 7.5.0 Update Package 9 Interim Fix 01 to Interim Fix 03
  • QRadar Incident Forensic 7.5.0 Update Package 10
  • QRadar Incident Forensic 7.5.0 Update Package 10 Interim Fix 01 to Interim Fix 02

This document does not cover all 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 11 Software Update


These instructions guide you through the process of upgrading an existing QRadar version to QRadar Incident Forensic 7.5.0 Update Package 11. 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 11 from the IBM Fix Central website:    https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FOther+software%2FIBM+Security+QRadar+Incident+Forensics&fixids=7.5.0-QRADAR-QIFSFS-20250122185136&source=SAR&function=fixId&parent=IBM%20Security

    Important:  Please confirm that you are installing the latest SFS file posted on 03/17/2025.  The updated file sha256sum is 4a0264f9a56ad262e40a148275d30c2c9f9befc775ac98961e44b63dd7c77b68
  2. Use SSH to log in to your Console as the root user.
  3. To verify you have enough space (10GB) 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 10GB 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.11.20250122185136.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.
  4. To run AQL queries that use geographic data or the flags on the Log Activity tab, update to the latest database from Maxmind after you upgrade to 7.5.0 Update Package 11.

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":"LOB77","label":"Automation Platform"},"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":"LOB77","label":"Automation Platform"},"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:
17 March 2025

UID

ibm17181479

Page Feedback