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 SFS. These instructions are intended for administrators who are upgrading to QRadar Incident Forensics 7.5.0 Update Package 8 by using an SFS file.
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_SHA256A 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
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".
You must ensure that your deployment does not include hosts with LUKS encrypted partitions to successfully upgrade your system. For more information see, Upgrading QRadar SIEM.
During the synchronization process, the host status does not reflect the sync status of the HA hosts and the remote host status remains in standby.
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, and then add it to the deployment.
Leapp pretests are not supported on detached console HA
To run a Leapp pretest on a detached console HA that is not a removed HA from a existing deployment, complete the following steps.
- Run the following command:
/opt/qradar/bin/ssh_key_generating - Edit the /store/configservices/deployed/deployment.xml file to add the missing
mhIptag to the console node by using only one of the following methods:- Edit the file by adding the
mhIptag manually:
<managedHost xmlns="" hostName="hostName of the system" console="true" offsite="false" changed="false" id="1" privateIP="IP of the system" mhIp="Same as privateIP" publicIP="" natId="0"> - Edit the file by running the following command:
mhip=$(/opt/qradar/bin/myver -vi); sed -e "/mhIp=/ n; /console=\"true\"/s/>/ mhIp=\"$mhip\">/" /store/configservices/deployed/deployment.xml
- Edit the file by adding the
When you upgrade to 7.5.0 Update Package 8, the Leapp pretest fails if the tool detects any Network Interface Card (NIC) that uses kernel naming (eth) and multiple NICs existing on the same system. For more information on the known issue and the workaround, see https://access.redhat.com/solutions/4067471.
/opt/qradar/support/qappmanagerCannot send udp syslog to QRADAR_CONSOLE_IP from an app container on AppHost
In QRadar 7.5.0 Update Package 8, you can not send Syslog UDP to QRADAR_CONSOLE_IP from an app container on AppHost. For more information, see DT365799.
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.
- Reinstall QRadar from media. For more information, see Reinstalling QRadar from media.
- Replace the factory reinstall image in the recovery partition with a previous version. For more information, see https://www.ibm.com/support/pages/node/6490659.
In 7.5.0 Update Package 7 Interim Fix 5 and later, 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. To resolve this issue, you must upgrade to WinCollect 7.3.1 P3. For more information, see DT269649.
EAL: rte_mem_virt2phy(): cannot open /proc/self/pagemap: Permission denied EAL: Cannot use IOVA as 'PA' since physical addresses are not available
For more information, see DT364450.
After you upgrade to QRadar 7.5.0 Update Package 5, WinCollect 7.X agents can experience management or configuration change errors
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.
Resolved Issues
For a list of Known Issues links of resolved issues in QRadar Incident Forensic 7.5.0 Update Package 8, see Known Issues. The Known Issues search page allows users to search for Known Issues by versions 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 8:
- DT257036: Unbound-anchor.service is reaching out publicly to DNS root servers
- DT258217: False-positive offenses are produced after the restart of ecs-ep process
- DT258235: Null Pointer Exception in Regex Monitor causes perfromance issues in event parsing
- DT258345: Re-adding a managed host can appear to be hung at the final step in the 'Host is Being Added to Deployment' window
- DT258961: False Positive offenses produced where rules use reference set not conditions
- DT259134: Unknown offense created on destination QRadar when forwarding normalized data from Source QRadar
- DT259571: Dropped events in log source protocol queue after upgrade to QRadar 7.5.0 Up 7
- DT259793: CRE Rule seems to be affecting the parsing of ADE AQL Properties
- DT084375: The managed search results page can be slow to load in QRadar environments with a large amount of Ariel query handles
- DT133052: QRadar - High availability crossover enable fails with ssh StrictHostKeyChecking
- DT256838: 7.5.0 UP7 IF03 Java change causes Amazon Web Service Log Source Type to stop working
- DT251945: Retain option available on freshly installed High Availability (HA) systems from factory reinstall
- DT251920: Time server set during initial installation reset after running qchange
- DT252014: HA Setup fails with "failed to change group ownership error"
- DT252073: QRadar tunnel-monitor service incorrectly attempts to create connections from HA standby appliances
- DT252127: Common rule test 'Event or flow processed by custom rules engine' can display a Number Format Exception
- DT252102: When AQL properties created before 7.4.3 exist in the forwarding profile, offline forwarding is slow
- DT252089: Invalid byte sequence for encoding "UTF8" while accessing reference data API or UBA import user
- DT252090: Historical correlation offense summary page can display a 'file access error' when viewing grouped events
- DT245546: STIG hardening on QRadar 7.5.0 Update Package 7 might not set a boot password, forcing a reinstall
- DT241221: HA Secondary disk space issues can occur when files for older versions of ECS are not removed
- DT244451: Hostcontext can exceed the default 256MB allocation, leading to out of memory issues on hosts
- DT244446: Custom rules: Match count rules do not trigger as expectedly when used with coalescing log sources
- DT244729: Log File protocol configured to connect with SFTP can stop collecting events unexpectedly in 7.5.0 UP7
- DT252131: Rule Wizard displays a blank pop up for the 'Name of the flow source is one of these sources' test
- DT252139: Asset details window does not display the latest email address when changed
- DT252100: Reference Table value incorrectly displayed in the rule responses of the Rule Wizard when edited
- DT259368: QRadar Applications failing to install/update after upgrading to QRadar 7.5.0 UP6
- DT224076: Rule Wizard displays 'The response count must be 0 or greater' when enabling response limiters with non-english UI locales.
- DT238257: Nightly backups fail if applications are in error status
- DT251980: Rule "Source/Destination asset weight is low" can trigger when weight is higher than the defined parameter
Upgrade information
QRadar Incident Forensic 7.5.0 Update Package 8 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.20240302192142 SFS file can upgrade the following QRadar Incident Forensic versions to QRadar Incident Forensic 7.5.0 Update Package 8:
- QRadar Incident Forensic 7.5.0 Update Package 7
- QRadar Incident Forensic 7.5.0 Update Package 7 Interim Fix 01
- QRadar Incident Forensic 7.5.0 Update Package 7 Interim Fix 02
- QRadar Incident Forensic 7.5.0 Update Package 7 Interim Fix 03
- QRadar Incident Forensic 7.5.0 Update Package 7 Interim Fix 04
- QRadar Incident Forensic 7.5.0 Update Package 7 Interim Fix 05
- QRadar Incident Forensic 7.5.0 Update Package 7 Interim Fix 06
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. To update appliances in parallel, see: QRadar: How to Update Appliances in Parallel.
Procedure
- Download the software update to install QRadar Incident Forensic 7.5.0 Update Package 8 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-20240302192142&includeSupersedes=0&source=fc
- Use SSH to log in to your Console as the root user.
- 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.
- 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 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.
- 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 10GB 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-QIFSFS-2021.6.8.20240302192142.sfs /media/updates
- To run a Leapp pretest, type the following command:
/media/updates/installer --leapp-only
- 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 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.
- The all option updates the software on all appliances in the following order:
Installation wrap-up
- After the system reboot is not initiated 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 Incident Forensic interface.
Product Synonym
QRadar Incident Forensics
Was this topic helpful?
Document Information
Modified date:
17 October 2024
UID
ibm17145148