IBM Support

Release of the QRadar 7.3.1 Patch 7 ISO (7.3.1.20181123182336)

Release Notes


Abstract

This technical note contains a list of the installation instructions, new features, and includes a resolved issues list for the release of IBM Security QRadar 7.3.1 Patch 7 ISO (7.3.1.20181123182336). This software update applies to QRadar SIEM, QRadar Vulnerability Manager, and QRadar Risk Manager. These instructions are intended for administrators who are upgrading from QRadar 7.2.8 Patch 1 or later to QRadar 7.3.1 Patch 7.

Content

What's new


For information on what's new in QRadar 7.3.1, see: https://www.ibm.com/support/knowledgecenter/SS42VS_7.3.1/com.ibm.qradar.doc/c_qradar_ov_whats_new_731.html

About this upgrade


These instructions are intended to assist you when you update appliances from QRadar 7.2.8 to QRadar 7.3.1 Patch 7 by using an ISO file. This ISO can update QRadar SIEM, QRadar Risk Manager, and QRadar Vulnerability Manager products from QRadar 7.2.8 to 7.3.1. If you have a software installation, need the latest memory requirements, or are making use of off-board storage, review the QRadar Upgrade Guide to prevent issues.

See QRadar: Software update check list for administrators for a list of steps to review before updating your QRadar deployment.

Products Version ISO File Upgrades to QRadar 7.3.1 Patch 7?
QRadar SIEM
QRadar Vulnerability Manager
QRadar Risk Manager
QRadar Log Manager
7.2.8 Patch 1 to 7.2.8 Patch 10 (or latest version) Yes, use these release notes to complete this process.
QRadar Incident Forensics 7.2.8 Patch 1 to 7.2.8 Patch 10 (or latest version) See the QRadar Incident Forensics ISO and release notes.
QRadar Network Insights 7.2.8 Patch 3 to 7.2.8 Patch 10 (or latest version) See the QRadar Network Insights ISO and release notes.
QRadar SIEM
QRadar Vulnerability Manager
QRadar Risk Manager
QRadar Log Manager
QRadar Network Insights
QRadar Incident Forensics
7.3.0 (any patch version) No, use the 7.3.1 SFS file. For more information, see the QRadar 7.3.1 SFS Release Notes .
QRadar Network Packet Capture 7.3.0 Build 1601 No, see the QRadar Network Packet Capture release notes .
QRadar Packet Capture 7.2.8 Build 278 No, see one of the following release notes:
QRadar Packet Capture 7.3.1
QRadar Packet Capture 7.3.1 Software Installs (your hardware)

*This document does not cover all the installation messages and requirements, such as changes to memory requirements or browser requirements for QRadar. To review any additional requirements, see the QRadar Upgrade Guide .

image-20181119152840-2
Figure 1: If you have QRadar 7.2.8 or later installed, you are not required to install each ISO release to update to QRadar 7.3.1 Patch 7.


Administrator notes

  1. This update includes a change to how login authentication works for fallback LDAP, Radius, or Active Directory on administrator accounts. If the external authentication server is unavailable, not all administrators are able to revert to local administrator passwords without a configuration change. This change was implemented in QRadar 7.3.0 Patch 4 or later. This note is included in 7.3.1 Patch 6 to raise awareness for this change. For more information, see QRadar: External Authentication Fails Due to Password Fallback Change for Administrators .
  2. TLS v1.0 and TLSv1.1 is disabled in this release. Connections to the user interface for legacy browsers might be rejected.
  3. WinCollect agents at version 7.2.2-2 or older use TLSv1.0 and TLS v1.1 connections to upgrade agents, which is disabled in QRadar 7.3.1 (all patch versions). If you have managed WinCollect agents, you must upgrade to WinCollect 7.2.5 before you install QRadar 7.3.1 Patch 6. WinCollect 7.2.5 is a pre-requisite for QRadar 7.3.1 Patch 3. Standalone WinCollect agents are not impacted by this requirement.
  4. Customized routes or static routes that are configured manually in QRadar are not preserved after the upgrade to QRadar 7.3.1 Patch 6 completes.
  5. Any iptables rules that you configured should be reviewed and noted for clean-up post installation. The interface names have changed in QRadar 7.3.1 Patch 7 due to the Red Hat Enterprise 7 operating system updates; if you reference the interfaces you must manually update the iptables rules.
  6. Each HA appliance must be updated individually by using the ISO file. The SFS file can allow the primary appliance to update the secondary, but the ISO file does not support this functionality. If you run the ISO setup on an HA primary, wait for the update to complete, and then run the setup on the HA secondary.
  7. There is no patch "All" option because QRadar 7.3.1 Patch 7 uses an ISO file to upgrade. The ISO must be mounted on the appliance and run locally on each host. If you have a software installation, you need your Red Hat Enterprise ISO and the QRadar ISO. If you have software installations on your own hardware you must read the QRadar Upgrade Guide to understand how to partition your systems appropriately.
  8. The QRadar 7.3.1 Patch 7 upgrade will take longer than expected due to the kernel changes to Red Hat 7 Enterprise. Early upgrade customers are reporting 2 to 2.5 hours to upgrade the Console appliance. You should be aware of this longer time frame and plan maintenance accordingly.
  9. Utilities or custom scripts that power users might have created for their QRadar deployment should be copied off the system. During the QRadar 7.3.1 Patch 7 update a warning is displayed that only data in /store is going to be preserved. After the appliance reboots, any scripts, 3rd party accounts, or utilities in /tmp, or /, or /root are deleted. ISO files that were mounted initially by using /root, are not impacted because this cleanup occurs later in the installation procedure.

Before you upgrade


Ensure that you take the following precautions:

  • Back up your data before you begin any software upgrade and verify that you have recent configuration backups that match your existing Console version. If required, take an on demand configuration backup before you begin. For more information about backup and recovery, see the QRadar Administration Guide .
  • HA appliances should have primaries in the online state and secondary as standby for their HA pair status.
  • If you have off-board storage configured, see the QRadar Upgrade Guide . There are special instructions for administrators with /store using off-board storage.
  • If you installed QRadar as a software installation on your own hardware, see the QRadar Upgrade Guide for partition information.
  • WinCollect 7.2.5 is a pre-requisite for QRadar 7.3.1 Patch 7; all managed agents must be updated. Standalone WinCollect agents are not impacted by this requirement.
  • All appliances in the deployment must be at the same software and patch level in the deployment.
  • Verify that all changes are deployed on your appliances. The update cannot install on appliances that have undeployed changes.
  • A QRadar 7.3.1 Patch 7 ISO is available to upgrade from QRadar 7.2.8 Patch 1 or install a new appliance or virtual machine. Review the QRadar Installation Guide .
  • To avoid access errors in your log file, close all open QRadar user interface sessions.
  • If you are unsure of the IP addresses or hostnames for the appliances in the deployment, run the /opt/qradar/support/deployment_info.sh utility to get a CSV file that contains a list of IP addresses for each managed host.
  • If you are unsure of how to proceed when reading these instructions or the documentation, it is best to ask before you start your upgrade. To ask a question in our forums, see: http://ibm.biz/qradarforums .

Part 1. Staging files and pretesting your deployment (required)


It is important that you pretest your deployment to ensure that you don't experience unexpected issues when you update to QRadar 7.3.1. A pretest is a common precaution before you install an update so that you can locate potential issues. The pretest does not restart services and can be completed without scheduled downtime. The pretest typically takes between 3 to 5 minutes to complete on each appliance. If for some reason your SSH session is disconnected, you can reconnect to the remote host using screen.

Procedure
The pretest should be completed on all hosts before you attempt to upgrade to QRadar 7.3.1 Patch 7.

  1. Download the QRadar 7.3.1 Patch 7 ISO (5 GB) 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-QRFULL-20181123182336&function=fixId&parent=IBM%20Security

    IMPORTANT: QRadar Incident Forensics and QRadar Network Insights use a unique ISO file to upgrade from 7.2.8 to 7.3.1 Patch 7. See the Fix Central page for those products to download the correct file.

  2. Use SSH to log in to your Console as the root user.
  3. Type the following command: screen
  4. To make the directory for the update, type:
    /opt/qradar/support/all_servers.sh -k "mkdir -p /media/cdrom || umount /media/cdrom"
  5. To verify that you have enough space (4GB) in /tmp for the ISO on all appliances, type:
    /opt/qradar/support/all_servers.sh -k df -h /root /var/log | tee diskchecks.txt
    • Best directory option: /root
      It is available on all appliance types, and is the best option to host the ISO file.
    • 2nd best directory option: /var/log
      This directory is available on all appliances, but there might not be the required space available.
    • DO NOT USE: /tmp, /store/tmp, or /store/transient for your ISO upgrade. These directories are partitioned as part of the upgrade; you cannot use them as storage locations or mount points for the ISO file.

      If the disk check command fails, retype the quotation marks from your terminal, 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 5GB of space available in a directory to copy the ISO 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 5GB available.

      Reminder: Utilities or custom scripts that you have created for QRadar should be copied off the system. During the 7.3.1 update a warning is displayed that only data in /store will be preserved. Therefore, Scripts, 3rd party utilities in /tmp, or /, or /root will be deleted during the upgrade.

  6. If there is not 4GB of space in /root or /var/log, you must make directory space for the ISO file.
  7. Using WinSCP or SCP, copy the ISO to the /root or /var/log directory on the QRadar Console with 4GB of disk space for the ISO file.
  8. To copy the files to all appliances, type: /opt/qradar/support/all_servers.sh -k -p /root/Rhe764QRadar7_3_1_20181123182336.stable-7-3-1.iso -r /root
  9. To check for any previously mounted files in the /media/updates directory, type the following command:
    df -h
  10. You must unmount any previously mounted files before you mount this software update file. To unmount any previously mounted files, type the following command:
    umount /media/cdrom
  11. To mount the ISO on all appliances, type the following command: /opt/qradar/support/all_servers.sh -C -k "mount -o loop /root/Rhe764QRadar7_3_1_20181123182336.stable-7-3-1.iso /media/cdrom"
  12. To pretest the Console appliance, type: /media/cdrom/setup -t
    The pretest output is written to the command window. Review this output after the pretest completes.
  13. Use SSH to open an SSH session to the other appliances in your deployment. QRadar Support recommends that you run the pretest on each host to identify issues before the update begins.
  14. To pretest the managed host, type: /media/cdrom/setup -t

    Results
    If an appliance in your deployment fails the pretest, take the recommended action from the pretest utility. The issue must be resolved before the update to QRadar 7.3.1 Patch 7 begins to prevent downtime for specific appliances. If there are messages you do not understand or want to discuss further, you can use our forums at http://ibm.biz/qradarforums to get advice. You can also open a ticket directly with QRadar Support ( http://ibm.biz/qradarsupport ).

Part 2. Installing the QRadar 7.3.1 Patch 7 ISO on the Console Appliance


These instructions guide you through the process of upgrading an existing QRadar installation at 7.2.8 Patch 1 or later to QRadar 7.3.1 Patch 7. The update on the Console must be completed before you attempt to update any managed hosts to QRadar 7.3.1 Patch 7.

Procedure
You must complete the Staging files and pretesting your deployment procedure before you begin the installation steps.

  1. Use SSH to log in to the Console as the root user.
  2. To run the ISO installer on the Console, type the following command: /media/cdrom/setup

    Important: Upgrading from QRadar 7.2.8 Patch 1 or later to QRadar 7.3.1 Patch 7 should take approximately 2 hours on a Console appliance.

  3. Wait for the Console primary update to complete.
  4. If you have an HA Secondary, you can now update the secondary appliance.
  5. Open an SSH session to the HA Console secondary.
  6. Type the following command to update the secondary Console: /media/cdrom/setup
  7. Wait for the HA Console secondary to complete the update.

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.

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)


Results
A summary of the ISO installation advises you of any issues. If there are no issues, use SSH to log in to the managed hosts and start the installer on each host to run the setup in parallel.

Part 3. Installing the QRadar 7.3.1 ISO on all other managed hosts


After the Console and Console HA secondary are updated to QRadar 7.3.1, the rest of the deployment can be updated. After the Console is updated, you can update Event Processors, Event Collectors, QFlow appliances in any order. You must open an SSH session to each host to run the setup command. The all_servers.sh utility cannot be used to start ISO installations.


If any of your appliances are HA pairs, you must upgrade the primary appliance first.


Procedure

  1. Use SSH to log in to the Console as the root user.
  2. Open an SSH session to each managed host and type the following command: /media/cdrom/setup

    Important: Upgrades for managed hosts should take approximately 1.5 hours.

  3. Wait for the managed host update to complete.
  4. If you have an HA Secondary, you can now update the secondary appliance.
  5. Open an SSH session to the manage host HA secondary.
  6. Type the following command to update the secondary: /media/cdrom/setup
  7. Wait for the HA Console secondary to complete the update.

    Results
    A summary of the ISO installation advises you of any issues. If there are no issues, run the ISO setup on the Console HA secondary appliance, if you have an HA pair. If you do not have a Console in HA, you can then start SSH sessions to each host and run the setup in parallel.

Part 4. Installation wrap-up

  1. After all hosts are updated, advise your team that they must clear their browser cache before logging in to QRadar SIEM.
  2. To unmount the /media/cdrom directory on all hosts, type:
    /opt/qradar/support/all_servers.sh -C -k "umount /media/cdrom"
  3. Delete the ISO from all appliances.
  4. If you use WinCollect agents version 7.2.6 or later, you must reinstall the SFS file on the QRadar Console. This is due to issues where the ISO replaces the SFS on the Console with WinCollect 7.2.5 as described here: APAR IV96364 . To install the latest WinCollect SFS on the Console, see the WinCollect release notes: WinCollect 7.2.7 Release Notes .
  5. Review any static routes or customized routing. As mentioned in the administrator notes, all routes were removed and will need to be reconfigured after the upgrade completes.
  6. Review any iptable rules that are configured to see if the interface names that have changed in QRadar 7.3.1 due to the Red Hat Enterprise 7 operating system updates affect them. Update any iptables rules that use Red Hat 6 interface naming conventions.

Resolved issues for QRadar 7.3.1 Patch 7


Some APAR links in the following table might take 24 hours to display properly after a software release is posted to IBM Fix Central. Several of these issues were fixed in 7.2.8 and 7.3.0 versions and exist in the 7.3.1 Patch 7 software update. For this reason, some APARs state that they were fixed in earlier releases, but are displayed as part of the QRadar 7.3.1 Patch 7 resolved issues list.

Resolved issues in QRadar 7.3.1 Patch 7
Product Component Number Description
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 IN A VULNERABILITY SEARCH
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 OFFENSES IJ09017 OFFENSES NOT GENERATED WHEN USING A CUSTOM EVENT PROPERTY AS OFFENSE INDEX IN HISTORICAL CORRELATION
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 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?


[{"Business Unit":{"code":"BU008","label":"Security"},"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Component":"Release Notes","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.3.1","Edition":"All Editions","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
03 October 2019

UID

ibm10741173