What's New in Version 5.29.2

The ThreatQuotient team is pleased to announce the availability of ThreatQ version 5.29.2. Below is a list of enhancements, important bugs that have been addressed, and upgrade instructions.

You can access these release notes, along with other ThreatQ product documentation on the ThreatQ Help Center.

Upgrade Impact

Some ThreatQ instances may require a reindex in conjunction with the upgrade which may increase the upgrade duration.  If so, the preflight check phase of the upgrade will identify if the upgrade requires a Solr reindex and require your confirmation before proceeding with the upgrade.

The upgrade is expected to take the standard amount of time for a ThreatQ upgrade. The exact time to complete the upgrade depends on your specific environment and resources. 

Customers upgrading to ThreatQ v5.19.0 or later may be prompted to enter the MariaDB root user password to apply Process and Connection Admin grants.

Upgrading from...	Data Migration Required	Server Reboot Required
5x (most recent version)

---

ThreatQ Platform (TQ)

The following is a bug fix for the ThreatQ platform.

Notable Bug Fixes

• In preparation for ThreatQ v6 migrations, we updated the backup process to back up operations from the docker volume.

---

Security and System Updates

The following Security update has been made:

• Remote CentOS Linux 7 host:

  Updated to	CESA REF
  Kernel 3.10.0	CVE-2022-42896 CVE-2023-38409 CVE-2023-45871 CVE-2023-4921 CVE-2024-1086 CVE-2024-26602 CVE-2023-4622 CVE-2023-2002 CVE-2023-2577 CVE-2023-4623 CVE-2020-3655

---

Install Notes

• To upgrade from a 4x version to versions 5.6 through 5.18, you must be on the most recent 4x release. To upgrade to 5.19 or later, you must first upgrade to release 5.13 or later.
• For the upgrade from the most recent 4x release to versions 5.6 through 5.18, you will need to enter your MariaDB root password during the upgrade process. To upgrade from 5.13 or later to 5.19 or later, you may need to enter your MariaDB root password during the upgrade process.
• The following warning will be displayed during the upgrade process:
  Warning: RPMD altered outside of yum.
**Found 5 pre-existing rpmdb problem(s), ‘yum’ check output follows
  This warning does not require any action on your part and will be resolved during the upgrade.
• Do not restart your instance during the upgrade process.

We highly recommend that you perform a backup of your ThreatQ instance before upgrading.

---

How to Upgrade

After you start the upgrade, do not cancel the installation. Doing so will leave your system in an unusable state.

Platform Check

ThreatQ version 5x provides you with the ability to run an independent preflight check, prior to upgrading, to ensure adequate disk space and to determine if a reindex is required. The system will also scan your installed integrations for any incompatible versions.  You will be unable to perform the upgrade if an incompatible integration version is detected. 

This scan does not apply to integrations installed on third-party systems such as the ThreatQ App for QRadar.

Run a platform check for the most recent ThreatQ version:

# sudo /usr/local/bin/tqadmin platform check

Run a platform check for a specific version:

# sudo /usr/local/bin/tqadmin platform check -v <version number> 

Upgrade Commands

To upgrade, run the following command:

# sudo /usr/local/bin/tqadmin platform upgrade

To upgrade to a specific version, run the following command:

# sudo /usr/local/bin/tqadmin platform upgrade -v <version number>

---

To discuss planning your upgrade, do not hesitate to get in touch with your Customer Success Engineer.

As always, contact our Customer Support Team if you encounter problems when upgrading or need assistance.

Thank you,

The ThreatQuotient Team

 support@threatq.com
support.threatq.com
 703.574.9893