Release Notes
Abstract
This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar 7.3.1 Patch 5 (7.3.1.20180720020816) 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 5.
Content
Upgrade information
QRadar 7.3.1 Patch 5 resolves 59 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-20180720020816 to upgrade to QRadar 7.3.1 Patch 5:
Current QRadar Version | Upgrades to QRadar 7.3.1 Patch 5? |
QRadar 7.2.8 (any patch version) | No, see QRadar 7.3.1 Patch 5 ISO Release Notes . |
QRadar 7.3.0 (any patch version) | Yes. Administrators can apply this SFS file to update to 7.3.1 Patch 5. |
QRadar 7.3.1 | Yes. Administrators can apply this SFS file to update to 7.3.1 Patch 5. |
The 7.3.1-QRADAR-QRSIEM-20180720020816 SFS file can upgrade QRadar 7.3.0 to QRadar 7.3.1 Patch 5. 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 5 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 5. For information about updating appliances in parallel, see: QRadar: How to Update Appliances in Parallel .
Procedure
- Download the software update to install QRadar 7.3.1 Patch 5 from the IBM Fix Central website: https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+SIEM&function=fixId&fixids=7.3.1-QRADAR-QRSIEM-20180720020816&includeRequisites=1&includeSupersedes=0&downloadMethod=http
- 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:
df -h - 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/updates - To mount the software update file to the /media/updates directory, type the following command:
mount -o loop -t squashfs /storetmp/731_QRadar_patchupdate-7.3.1.20180720020816.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:
1. Console.
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.
- The all option updates the software on all appliances in the following order:
Installation wrap-up
- 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.
Results
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.
Product | Component | Number | Description |
---|---|---|---|
QRADAR | SECURITY BULLETIN | CVE-2018-2579 | Multiple vulnerabilities in IBM Java Runtime affect IBM Cognos Command Center |
QRADAR | SECURITY BULLETIN | CVE-2013-1768 | OpenJPA as used in IBM QRadar SIEM is vulnerable to remote code execution |
QRADAR | SECURITY BULLETIN | CVE-2017-1695 | IBM QRadar SIEM uses outdated hash algorithms |
QRADAR | SECURITY BULLETIN | CVE-2017-3736 | Security vulnerability in OpenSSL |
QRADAR | SECURITY BULLETIN | CVE-2018-2579 | Rational Build Forge Security Advisory for Apache Tomcat |
QRADAR | USER INTERFACE | IJ05185 | UNABLE TO EDIT QRADAR LDAP CONFIGURATION AFTER A PREVIOUSLY MAPPED USER ROLE OR SECURITY PROFILE IS DELETED |
QRADAR | USER INTERFACE | IV97787 | THE QRADAR ASSET TAB CAN BE SLOW TO LOAD WHEN THERE ARE A LARGE NUMBER OF ASSET VULNERABILITY INSTANCES |
QRADAR | SEARCHES | IJ06611 | POP UP WINDOW WITH NO SEARCH RESULTS WHEN DRILLING DOWN INTO SEARCH RESULTS |
QRADAR | SEARCHES | IJ05806 | SOME LOG ACTIVITY SEARCHES STOP RETURNING RESULTS FROM LOG SOURCE GROUPS AFTER PATCH/UPGRADE TO QRADAR 7.3.1 |
QRADAR | REPORTS | IJ06278 | RUNNING A LOG SOURCE REPORT AGAINST AN EMPTY LOG SOURCE GROUP RETURNS ALL LOG SOURCES |
QRADAR | REPORTS | IJ05341 | 'EXPORT TO XML' OR 'EXPORT TO CSV' FROM THE QRADAR ASSETS TAB CAN SOMETIMES UNEXPECTEDLY STOP/FAIL |
QRADAR | SEARCHES | IJ04906 | USING THE RIGHT-CLICK FILTER 'SOURCE OR DESTINATION IP IS...' IN A LOG ACTIVITY SEARCH DOES NOT WORK AS EXPECTED |
QRADAR | SEARCHES | IJ03405 | AQL SEARCHES THAT OPEN THE LOG ACTIVITY PAGE AFTER COMPLETING CAN DISPLAY UNEXPECTED HTML CHARACTERS |
QRADAR | SEARCHES | IJ00489 | COMMAS ARE SWITCHED TO 'OR' WHEN MULTIPLE CUSTOM EVENT PROPERTIES ARE CONTAINED IN A SEARCH |
QRADAR | OFFENSES | IV99417 | OFFENSE START TIMES CAN JUMP BACK IN TIME IF CUSTOMER HAS LONG RUNNING OFFENSES AND LONG DELAY BETWEEN START AND STORAGE TIME. |
QRADAR | SEARCHES | IV85637 | TOP SOURCES AND TOP DESTINATION DASHBOARD SEARCHES REPORT DATA FROM ALL DOMAINS NOT JUST THE CONFIGURED ONES |
QRADAR | FLOWS | IV84601 | CATEGORIZATION OF OFF-SITE SOURCE AND TARGET FOR FLOWS DISPLAYS AS 'UNKNOWN' AND APPLICATION DISPLAYS AS 'OTHER' |
QRADAR | EVENTS | IJ06381 | EVENTS FORWARDED VIA AN OFFENSE RULE DO NOT HAVE A VALID SYSLOG HEADER APPENDED |
QRADAR | EVENTS | IJ05338 | EVENT COLLECTION CAN STOP DUE TO A BUFFER UNDERFLOW EXCEPTION IN ECS-EC REQUIRING AN ECS-EC-INGRESS SERVICE RESTART |
QRADAR | LOG SOURCES | IJ04654 | LOGFILE PROTOCOL LOG SOURCES CAN STOP WORKING, FAIL TO CONNECT WITH ERROR 'ALGORITHM NEGOTIATION FAIL' IN CONFIG WINDOW |
QRADAR | OFFENSES | IJ04225 | USING THE QRADAR API "GET /SIEM/OFFENSE" TO RETRIEVE A LIST OF OFFENSES CAN TAKE LONGER THAN EXPECTED TO COMPLETE |
QRADAR | LICENSES | IJ02819 | '...SENT A TOTAL OF XXXX EVENT(S) DIRECTLY STORAGE...QUEUE IS AT 0 PERCENT CAPACITY" DURING OVER LICENSE EPS SPIKES |
QRADAR | OFFENSES | IJ00971 | AN APPLICATION ERROR MAY OCCUR IN THE OFFENSE TAB WHEN THE END TIME FOR AN OFFENSE IS IN THE FUTURE |
QRADAR | CUSTOM EVENTS | IJ00878 | CUSTOM EVENT PROPERTY WITH SPACE IN ITS NAME IS NOT FORWARDED TO THE DESTINATION |
QRADAR | SEARCHES | IJ05096 | QUICK SEARCHES CONTAINING AN 'AND' OPERATOR CAN SOMETIMES FAIL TO PROGRESS TO COMPLETION |
QRADAR | LICENSES | IJ03439 | CLICKING THE 'SUSPECT CONTENT' ICON DISPLAYS A BLANK PAGE WHEN NO APPROPRIATE LICENSE IS INSTALLED/CONFIGURED |
QRADAR NETWORK INSIGHTS | TRAFFIC | IJ01001 | QNI CLASSIFIES LDAP TRAFFIC AS FTP TRAFFIC |
QRADAR | FLOWS | IJ02836 | NO FLOWS BEING RECEIVED FROM A QFLOW APPLIANCE |
QRADAR | DATABASE | IJ04314 | QRADAR DATABASE REPLICATION TO MANAGED HOSTS CAN FAIL WHEN THE CONSOLE /STORETMP HAS INSUFFICIENT FREE SPACE AVAILABLE |
QRADAR | DATA | IJ03316 | DATA BACKUPS FAIL WHEN EVENT/FLOW LOG HASHING IS ENABLED |
QRADAR | LOG SOURCES | IJ02749 | 'TARGET EXTERNAL DESTINATIONS' BECOMES UNSELECTED AFTER PERFORMING A 'BULK EDIT' OF LOG SOURCES |
QRADAR | RULES | IJ02262 | RULES IMPORTED FROM A SYSTEM WITH CONFIGURED DOMAINS TO A SYSTEM WITHOUT DOMAINS CAN SEE REFERENCE SET DATA ISSUES |
QRADAR | UPGRADE | IJ06277 | UPGRADE TO 7.3.X FAILS AND PROMPTS FOR REDHAT ISO WHEN /VAR/LOG/INSTALL.LOG IS MISSING |
QRADAR | UPGRADES | IJ05311 | GARP REQUEST DURING HA_SETUP.SH CAN SOMETIMES BE BLOCKED BY A NETWORK SWITCH PREVENTING ARP TABLES FROM BEING UPDATED |
QRADAR | UPGRADES | IJ05110 | A FAILED AND ROLLED BACK PATCH ATTEMPT FROM 7.3.0.X TO 7.3.1.X CAN CAUSE ISSUES WHEN ATTEMPTING TO PATCH AGAIN |
QRADAR | UPGRADES | IJ04472 | RECOVERY REINSTALL ON A HIGH AVAILABILITY PRIMARY CAN FAIL DISPLAYING AS 'UNKNOWN' STATE IN SYSTEM AND LICENSE WINDOW |
QRADAR | UPGRADES | IJ03981 | QRADAR UPGRADE AND/OR PATCH FAILS WITH 'ERROR EXECUTING 34-POSTGRESQL-UPGRADE.SH' WHEN UNEXPECTED DATABASE EXIST |
QRADAR | UPGRADES | IJ00104 | QRADAR UPGRADE TO 7.3.0.X CAN FAIL "...GENERATE_ENVIRONMENT.SH: OPTION REQUIRES AN ARGUMENT -- N" |
QRADAR | APPLIANCES | IJ05193 | SOME QRADAR SOFTWARE APPLIANCES ARE NOT ABLE TO ADD A QVM SCANNER IN THE QRADAR USER INTERFACE |
QRADAR | SECURITY | IJ01123 | Q1X509TRUSTMANAGER LEAKS FILE HANDLES IF THERE IS A TRUST STORE IN /OPT/QRADAR/CONF/TRUSTED_CERTIFICATES |
QRADAR | DEVICES | IJ02635 | 'APPLICATION ERROR' WHEN PERFORMING A NORMALIZED DEVICE COMPARISON FOR A PALO ALTO DEVICE |
QRADAR VULNERABILITY MANAGER | SCANS | IJ06302 | SCAN EXPORT DOES NOT HONOR SPECIFIED VULNERABILITIES THAT ARE CONFIGURED IN THE SCAN POLICY |
QRADAR VULNERABILITY MANAGER | DOMAINS | IJ01180 | INTERACTION WITH IBM BIGFIX AND QVM CAN FAIL WHEN DOMAIN AUTHENTICATION IS USED |
QRADAR VULNERABILITY MANAGER | ASSETS | IJ00941 | EXCEPTIONED VULNERABILITIES ARE STILL APPEARING IN MANAGE VULNERABILITY VIEW FOR SOME ASSETS |
QRADAR | EVENTS | IJ02457 | UNPARSED CRE EVENTS CONTAINING 'WHERE CATEGORY BETWEEN..." OBSERVED WHEN USER BEHAVIOR ANALYTICS (UBA) APP INSTALLED |
QRADAR | REPORTS | IJ04421 | REPORTS CAN FAIL TO RUN WHEN EVENT AND/OR FLOW HASHING WITH HMAC IS ENABLED IN ARIEL DATABASE SETTINGS |
QRADAR | LOGS | IV98932 | /VAR/LOG/ PARTITION CAN BECOME FILLED DUE TO REPEATED TEST EXCEPTION MESSAGES BEING LOGGED |
QRADAR | SCANS | IV97516 | 'WHEN THE DESTINATION IS VULNERABLE TO CURRENT EXPLOIT ON ANY PORT' RULE TEST STOPS WORKING AFTER VULNERABILITY SCAN |
QRADAR | USER INTERFACE | IJ06084 | SETTING A DELEGATED ADMINISTRATION PERMISSION FOR 'MANAGE REFERECE DATA' ONLY DOES NOT ALLOW ACCESS TO ADMIN TAB |
QRADAR | API | IJ06032 | CHANGES MADE WITHIN THE INCLUDED QRADAR API CHANGED HOW SOME QRADAR APPS FETCH DATA (EG. USER BEHAVIOR ANALYTICS - UBA) |
QRADAR | SEARCHES | IJ05712 | QRADAR REFERENCE SET DATA FILTER SEARCHES (MANUAL AND WITHIN SOME APPS) CAN TAKE LONGER THAN EXPECTED TO COMPLETE |
QRADAR | SEARCHES | IJ05109 | USING A FILTER CONTAINING A COMMA OPERATOR IN THE REGEX DOES NOT WORK WITH 'WHEN THE EVENT MATCHES THIS SEARCH FILTER' RUL |
QRADAR | EVENTS | IJ04903 | 'THIS INFORMATION SHOULD SET OR REPLACE THE NAME OF THE ASSOCIATED OFFENSE' NOT ALWAYS WORKING AS EXPECTED |
QRADAR | SEARCHES | IJ03209 | 'ADD' BUTTON DOES NOT WORK WHEN AN 'EQUALS ANY OF' CONDITION IS PRESENT WITHIN THE RULE WIZARD WITH MORE THAN ONE PROPERTY |
QRADAR | RULES | IJ02670 | RULE TEST 'AND WHEN THE URL (CUSTOM) IS CATEGORIZED BY X-FORCE AS ONE OF THE FOLLOWING CATEGORIES' CAN SOMETIMES FAIL TO FIRE |
QRADAR | REFERENCE SETS | IJ02533 | ERROR 'JAVA.LANG.NUMBERFORMATEXCEPTION:EMPTY STRING' IS GENERATED WHEN ATTEMPTING TO ADD REFERENCE SET VALUES |
QRADAR | RULES | IJ02437 | BUILDING BLOCKS CAN FAIL TO WORK AS EXPECTED WHILE RULES ARE BEING RELOADED |
QRADAR | RULES | IJ00772 | REGULAR EXPRESSIONS IN THE RULE EDITOR DO NOT WORK WITH JAPANESE CHARACTORS |
QRADAR | SERVICES | IJ02782 | REQUIRED SERVICES RESTART IS NOT PERFORMED AFTER SWITCH FROM DAYLIGHT SAVING TIME TO STANDARD TIME |
QRADAR | USER INTERFACE | IJ07150 | REPORT GROUPS ARE SOMETIMES NOT SHAREABLE FROM AN ADMIN TO A NON-ADMIN USER |
QRADAR INCIDENT FORENSICS | FORENSICS DECAPPER | IJ07872 | QRADAR NETWORK INSIGHTS STOPS PROCESSING FLOWS, PACKETS DROPPED BY THE DECAPPER |
QRADAR | SECURITY | IJ06000 | UNEXPECTED DIVIDE BY ZERO EXCEPTION |
QRADAR | SEARCHES | IJ08848 | ARIEL_PROXY_SERVER CAN GO OUT OF MEMORY DURING SEARCHES ON LARGE MULTI-CPU APPLIANCES DUE TO DEFAULT TUNING PARAMETER |
Where do I find more information?
Was this topic helpful?
Document Information
Modified date:
07 January 2019
UID
ibm10713755