Release of the QRadar 7.3.1 Patch 7 SFS (184.108.40.20681123182336)
This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar 7.3.1 Patch 7 (220.127.116.1181123182336) SFS. These instructions are intended for administrators who use an SFS file to upgrade from QRadar 7.3.1 to QRadar 7.3.1 Patch 7.
QRadar 7.3.1 Patch 7 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. The software update can update all appliances attached to the QRadar Console. If you have installed any of the following QRadar versions, install software update 7.3.1-QRADAR-QRSIEM-20181123182336 to upgrade to QRadar 7.3.1 Patch 7:
|Current QRadar Version||Upgrades to QRadar 7.3.1 Patch 7?|
|QRadar 7.2.8 (any patch version)||No, see QRadar 7.3.1 Patch 7 ISO Release Notes .|
|QRadar 7.3.0 (any patch version)||Yes. Administrators can apply this SFS file to update to 7.3.1 Patch 7.|
|QRadar 7.3.1||Yes. Administrators can apply this SFS file to update to 7.3.1 Patch 7.|
The 7.3.1-QRADAR-QRSIEM-20181123182336 SFS file can upgrade QRadar 7.3.0 to QRadar 7.3.1 Patch 7. However, this document does not cover all 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 updating 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 software update for QRadar 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 .
Installing the QRadar 7.3.1 Patch 7 Software Update
These instructions guide you through the process of upgrading an existing QRadar version from 7.3.1 to QRadar 7.3.1 Patch 7. For information about updating appliances in parallel, see: QRadar: How to Update Appliances in Parallel .
- Download the software update to install QRadar 7.3.1 Patch 7 from the IBM Fix Central website: https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FOther+software%2FIBM+Security+QRadar+Vulnerability+Manager&fixids=7.3.1-QRADAR-QRSIEM-20181123182336&function=fixId&parent=IBM%20Security
- Use SSH to log in to your Console as the root user.
- To verify that you have enough space (3 GB) in /storetmp for the QRadar Console, type:
df -h /tmp /storetmp /store/transient | tee diskchecks.txt
- Best directory option: /storetmp
It is available on all appliance types, is not cleaned up if you need to postpone your update, and is available on all appliance types at all versions. In QRadar 7.3.0 versions /storetmp is a symlink to the /storetmp partition.
- 2nd best directory option: /tmp
This directory is available on all appliances, but in the 7.3.0 versions it is significantly smaller. Moving a file to this directory can cause services to stop. If you leave a file in /tmp for 10 days without completing the SFS update, it might get cleaned up by Red Hat's tmpwatch cron job.
- 3rd best option: /store/transient
The store/transient directory was introduced in QRadar 7.2.1 and is allocated 10% of the overall /store directory. However, this directory does not exist on all appliances, such as QFlow or QRadar Network Insights and might not be an actual partition on all appliances.
If the disk check command fails, retype the quotation marks from your terminal, and 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 3 GB 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 3 GB available.
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.
- Best directory option: /storetmp
- To create the /media/updates directory, type the following command: mkdir -p /media/updates
- Use SCP to copy the files to the /storetmp directory on the QRadar Console or a location with 3 GB of disk space.
- Change to the directory where you copied the software update file. For example, cd /storetmp
- To check for any previously mounted files in the /media/updates directory, type the following command:
- You must unmount any previously mounted files before you mount this software update file. To unmount any previously mounted files, type the following command:
- To mount the software update file to the /media/updates directory, type the following command:
mount -o loop -t squashfs /storetmp/731_QRadar_patchupdate-18.104.22.16881123182336.sfs /media/updates
- To run the software update 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 installation menu displays.
- Using the software update installer, select all.
- The all option updates the software on all appliances in the following order:
2. No order required for remaining appliances. All remaining appliances can be updated in any order 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 updated first. After the Console is updated, 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 update systems in series, you can update the Console first, then copy the software update to all other appliances and run the installer individually on each managed host. The Console must be updated 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 re-run the installer, the software update installation resumes.
Note: In QRadar 7.3.1 Patch 6, a kernel update was introduced to address issues with appliances failing to log in or list unit files. These issues could prevent the appliance from rebooting. This new kernel does not take effect until the appliance is rebooted. You might need to reboot your system manually for the kernel update to take effect.
- The all option updates the software on all appliances in the following order:
To work around this issue, do one of the following:
- If you are able to use SSH, type the following command: systemctl --force --force reboot
- If you are not able to use SSH, you must perform a cold reboot of the appliance. To do this, physically reboot the appliance or use Integrated Management Module (IMM)
- After the update completes and you have exited the installer, type the following command: umount /media/updates
- Clear your browser cache before logging in to the Console.
A summary of the software update installation advises you of any managed host 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, you can send an email to your team to inform them that they will need to clear their browser cache before logging in to the QRadar SIEM interface.
Known and Resolved Issues
Some APAR links in the following table might take 24 hours to display properly after a software release is posted to IBM Fix Central.
|QRADAR||SECURITY BULLETIN||CVE-2018-2952||Multiple vulnerabilities in IBM Java SDK and IBM Java Runtime affect IBM QRadar SIEM|
|QRADAR||SECURITY BULLETIN||CVE-2018-1728||IBM QRadar SIEM is vulnerable to Cross-Site Scripting|
|QRADAR||SECURITY BULLETIN||CVE-2018-8897||IBM QRadar SIEM is vulnerable to Using Components with Known Vulnerabilities|
|QRADAR||SECURITY BULLETIN||CVE-2018-1730||IBM QRadar SIEM is vulnerable to XML External Entity Injection|
|QRADAR||SECURITY BULLETIN||CVE-2018-8034||Apache Tomcat as used in IBM QRadar SIEM is vulnerable to publicly disclosed vulnerability|
|QRADAR||SECURITY BULLETIN||CVE-2018-8036||Apache PDFBox as used in IBM QRadar Incident Forensics is vulnerable to Publicly disclosed vulnerability|
|QRADAR||SECURITY BULLETIN||CVE-2017-1622||The Application framework within IBM QRadar SIEM is vulnerable to Improper Certificate Validation|
|QRADAR VULNERABILITY MANAGER||SEARCHES||IJ11732||"APPLICATION ERROR" WHEN PERFORMING AN ASSET SAVED SEARCH EQUALS
|QRADAR||PROCESSES||IJ11821||BUFFERUNDERFLOW EXCEPTION CAN OCCUR BETWEEN THE ECS-EC AND ECS-EP PROCESSES|
|QRADAR||USER INTERFACE||IJ10166||USERS CANNOT LOG INTO QRADAR DUE TO THREAD DEADLOCK|
|QRADAR||SEARCHES||IJ10862||EXPORTED ASSET SEARCHES CONTAINING A NETWORK FILTER CAN GENERATE BLANK XML OR CSV FILES|
|QRADAR||REPORTS||IJ05334||TABLE REPORT VALUE FORMATTING CAN DISPLAY INCORRECTLY FOR AQL AGGREGATED DATA|
|QRADAR||OFFENSES||IJ09017||OFFENSES NOT GENERATED WHEN USING A CUSTOM EVENT PROPERTY AS OFFENSE INDEX IN HISTORICAL CORRELATION|
|QRADAR NETWORK INSIGHTS||FLOWS||IJ08471||QRADAR NETWORK INSIGHTS CONTENT FLOWS ARE COUNTED AGAINST FLOW LICENSE WHEN THEY SHOULDN'T BE|
|QRADAR||UPGRADES||IJ08432||BACKLEVEL JTDS JAR FILES IN QRADAR 7.3.1 CAN SOMETIMES CAUSE AN OUT OF MEMORY WITH ECS-EC-INGRESS PROCESS|
|QRADAR||REPORTS||IJ09036||AQL QUERY WITH AN AGGREGATE THAT IS RUN AGAINST A CURSOR THAT CONTAINS AN AGGREGATE FAILS WITH 'GENRAL FAILURE'|
|QRADAR||REPORTS||IJ08228||CREATING AN AQL QUERY WITH A SUB-SELECT CAN CAUSE DASHBOARD TIMESERIES TO FAIL DUE TO THE GLOBAL VIEW CREATED|
|QRADAR||FLOWS||IJ11163||NETFLOW V9 / IPFIX INITIATOR/RESPONDER OCTET/PACKET FIELD DATA IS NOT PROCESSED BY QRADAR|
|QRADAR NETWORK INSIGHTS||FLOWS||IJ10158||QRADAR NETWORK INSIGHTS (QNI) DECAPPER 'OUT OF MEMORY' INSTANCES CAUSED BY MULTIPLE INSPECTOR COMPONENTS|
|QRADAR||APPLIANCES||IJ00712||A STANDBY HA MANAGED HOST REBUILT FROM THE RECOVERY IMAGE MAY NOT MERGE /STORE/TRANSIENT CORRECTLY CAUSING HA ISSUES|
|QRADAR||EVENTS||IJ04898||GEOGRAPHIC COUNTRY/REGION INDEXING CAN CAUSE UNEXPECTED EVENT COLLECTION INTERRUPTION WHEN GEODATA UPDATES OCCUR|
|QRADAR||APPLIANCES||IJ03438||/OPT/QRADAR/SUPPORT CAN RUN OUT OF FREE SPACE AFTER UPGRADE DUE TO A LARGE NUMBER OF FAILED REPLICATION FILES|
|QRADAR||OFFENSES||IJ10545||OFFENSE SOURCE SUMMARY DISPLAYS INCORRECTLY FOR OFFENSES INDEXED ON REGEX CUSTOM PROPERTIES WITH FIELD TYPE "IP"|
|QRADAR||UPGRADES||IJ10818||CHANGES MADE TO LOGROTATE IN QRADAR 7.3.1 PATCH 6 CAN CAUSE /VAR/LOG AND OR /OPT TO RUN OUT OF FREE SPACE|
|QRADAR||EVENTS||IJ03211||HOSTCONTEXT SERVICES CAN FAIL TO START DURING A HIGH AVAILABILITY (HA) FAILOVER TO SECONDARY EP/FP APPLIAN|
|QRADAR||DATA||IJ08827||HOSTCONTEXT STARTUP ON A MANAGED HOST CAN OCCUR PRIOR TO DATABASE VERIFICATION|
|QRADAR RISK MANAGER||DEVICES||IV93144||QRADAR RISK MANAGER DEVICE BACKUPS CAN FAIL WHEN THERE IS AN EMPTY VALUE IN AN PROTOCOL CONFIGURATION ADDRESS SET|
|QRADAR VULNERABILITY MANAGER||SCANS||IV99512||CONCURRENT SCHEDULED SCANS THAT INCLUDE IP EXCLUSIONS CAN FAIL TO START AT THE SCHEDULED TIME|
|QRADAR VULNERABILITY MANAGER||SCANS||IV91226||QVM SCAN CAN FAIL TO START/PROGRESS WHEN THERE ARE A LARGE NUMBER OF IP ADDRESS SCAN EXCLUSIONS DUE TO A POSTGRES EXCEPTION|
|QRADAR VULNERABILITY MANAGER||REPORTS||IJ09183||VULNERABILITY TRENDING REPORTS CAN SOMETIMES BE BLANK|
|QRADAR VULNERABILITY MANAGER||SEARCHES||IJ08226||CLICKING 'VIEW IN BY' IN A VULNERABILITY SEARCH DASHBOARD NAVIGATES TO INCORRECT QRADAR WINDOW|
|QRADAR VULNERABILITY MANAGER||SCANS||IJ07030||VULNERABILITY SCANS EXPERIENCE A DELAY PRIOR TO COMMENCING WHEN A HIGH NUMBER OF IP EXCLUSIONS ARE DEFINED|
|QRADAR VULNERABILITY MANAGER||SCANS||IJ03246||ALL SCHEDULED SCANS THAT RUN ON DECEMBER 1ST START AT MIDNIGHT NO MATTER WHAT TIME THEY ARE CONFIGURED TO START|
|QRADAR||DATA||IJ10999||UPDATES TO REFERENCE DATA USING CUSTOM EVENT PROPERTIES (CEP) CAN CAUSE CEP AND RULES TO BE RELOADED/TMP|
|QRADAR||OFFENSES||IJ10070||QRADAR CAN STOP GENERATING OFFENSES DUE TO AN INCORRECT NULL CHECK|
|QRADAR||RULES||IJ08227||CUSTOM RULE ENGINE DOES NOT USE LOG SOURCES CONTAINED IN 'OTHER' LOG SOURCE GROUP FOR FUNCTIONAL TEST PARAMETERS|
|QRADAR||USER INTERFACE||IJ10532||WINCOLLECT AGENT 'LAST HEARTBEAT' STATUS DISPLAYS AS "UNAVAILABLE" WHEN WORKING AS EXPECTED|
Where do I find more information?
More support for:
IBM QRadar SIEM
Component: Release Notes
Software version: 7.3.1
Operating system(s): Linux
Software edition: All Editions
Reference #: 0740889
Modified date: 07 January 2019