Release of the QRadar 7.3.1 Patch 4 Interim Fix 01 SFS (7.3.1.20180601192933)

Content

Upgrade information
This interim fix is intended to resolve specific issues reported in QRadar 7.3.1 Patch 4. This update requires that your deployment is installed with IBM QRadar 7.3.1 Patch 4.

The 7.3.1-QRADAR-QRSIEM-20180601192933 SFS file can upgrade QRadar 7.3.1 Patch 4 to QRadar 7.3.1 Patch 4 Interim Fix 01. 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.

See QRadar: Software update checklist for administrators for a list of steps to review before you update 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 IBM Security 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, administrators must review the instructions in the QRadar Installation Guide.

Installing the QRadar 7.3.1 Patch 4 Interim Fix 01 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 4 Interim Fix 01. For information about updating appliances in parallel, see: QRadar: How to Update Appliances in Parallel.

Procedure

1. Download the software update to install QRadar 7.3.1 Patch 4 Interim Fix 01 from the IBM Fix Central website: http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FIBM+Security+QRadar+Vulnerability+Manager&fixids=7.3.1-QRADAR-QRSIEM-20180601192933INT&source=SAR
2. Use SSH to log in to your Console as the root user.
3. To verify that you have enough space (3GB) in /store/tmp 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.1 versions /store/tmp is a symlink to the /storetmp partition.
   • 2nd best directory option: /tmp
     This directory is available on all appliances, but in 7.3.1 versions it is significantly smaller. Moving a file here 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.

     
     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 3GB 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 has less than 3GB available.

     
     Note: In QRadar 7.3.1 and later, an update to directory structure for STIG-compliant directories reduces the size of several partitions. This directory structure change can impact administrators who attempt to move large files to QRadar appliances.

4. To create the /media/updates directory, type the following command: mkdir -p /media/updates
5. Use SCP to copy the files to the /storetmp directory on the QRadar Console or a location with 3 GB of disk space
6. Change to the directory where you copied the patch file. For example, cd /store/tmp
7. To mount the software update file to the /media/updates directory, type the following command:
   mount -o loop -t squashfs /storetmp/731_QRadar_interimfix-7.3.1.20180507202600-IF01-20180601192933.sfs /media/updates
8. 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.
9. 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.

   • If you do not select the all option, you must select your Console appliance.
     
     As of QRadar 7.2.6 Patch 4 and later, administrators 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 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 administrators want to patch systems in parallel, they 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.
      
10. Wait for the update to QRadar 7.3.1 Patch 4 Interim Fix 01 to complete. The appliance will reboot to complete the installation.
    
    Results
    A summary of the software update installation advises you of any managed host that failed to update. If the software update fails to update a managed host, you can copy the software update to the host and run the installation locally.

Installation wrap-up

1. After all hosts are updated, advise your team that they must clear their browser cache before they log in to the QRadar SIEM interface.
2. To unmount the /media/cdrom directory on all hosts, type:
   /opt/qradar/support/all_servers.sh -C -k “umount /media/updates"
3. Delete the SFS file from all appliances.
   
   Results
   The installation is complete. For more information about the security fixes in this release, see the resolved issues list.

Resolved issues in QRadar 7.3.1 Patch 4 Interim Fix 01

Product	Component	Number	Description
QRADAR	SECURITY BULLETIN	CVE-2018-1612	IBM QRadar Incident Forensics is vulnerable to authentication bypass.
QRADAR	SEARCHES	IJ05096	QUICK SEARCHES CONTAINING AN 'AND' OPERATOR CAN SOMETIMES FAIL TO PROGRESS TO COMPLETION
QRADAR	EVENTS	IJ05338	EVENT COLLECTION CAN STOP DUE TO A BUFFER UNDERFLOW EXCEPTION IN ECS-EC REQUIRING AN ECS-EC-INGRESS SERVICE RESTART
QRADAR	DATA	IJ06032	CHANGES MADE WITHIN THE INCLUDED QRADAR API CHANGED HOW SOME QRADAR APPS FETCH DATA
QRADAR	LICENSES	IJ02819	'...SENT A TOTAL OF XXXX EVENT(S) DIRECTLY STORAGE...QUEUE IS AT 0 PERCENT CAPACITY" DURING OVER LICENSE EPS SPIKES

Where do I find more information?

---