Release notes - Guardium Insights Version 3.5.1

IBM® Guardium® Insights is a hybrid cloud data security hub that helps you improve visibility into user data activity and risk. Guardium Insights helps you protect data more efficiently, enhance information technology flexibility, and reduce operational costs as you embrace new business paradigms (such as moving data to the cloud). Guardium Insights helps reduce the cost and complexity related to collecting, managing, and retaining data security and compliance data. It provides new analytics to enhance threat investigations - and it provides quick reporting functionality (including prebuilt reports). Risk scoring and alerting in Guardium Insights help you prioritize your activities.

Version 3.4.x This content only applies to Guardium Insights Version 3.4.x.

Guardium Insights is a powerful tool that can help you secure your data. Simple to use, Guardium Insights allows you to set up connections to your data sources.

Guardium Insights provides tools to help you analyze data:

  • Outlier mining: Detecting anomalies in activities and exceptions.
  • Risk events: Identifying assets at risk using broad data points.
  • Reports: Dive into the raw data for deep investigation.

Contents

Download Guardium Insights v3.5.1

Guardium Insights V3.5.1 can be downloaded as an archive file (2.5.1.tar.gz) from: https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-guardium-insights

You can install only the products for which your site is entitled.

For further instructions, read the README.md file located after unzipping the latest tar file.

The Quick Start Guide for this offering is available at Passport Advantage (https://www.ibm.com/software/passportadvantage) (search for Part Number “M0H7GML”).

Install Guardium Insights v3.5.1

Important: When upgrading to version 3.5.0 or patching to 3.5.1 - or during a fresh installation of either of these two versions - a missing MongoDB image results in upgrade and installation failure. See Missing MongoDB image results in upgrade and installation failure to learn how to work around this problem.

Before installing Guardium Insights, review the system requirements: Guardium Insights v3.5.x system requirements and prerequisites

This offering is deployed as a new installation of Guardium Insights – or as an in-place upgrade. Please follow these instructions:

Important: See Preparing to patch or upgrade Guardium Insights to learn how to upgrade Guardium Insights for OpenShift Container Platform (OCP) and OpenShift Data Foundation (ODF) Version 4.14 support.

Guardium Insights v3.5.x release notes

Security fixes in Guardium Insights v3.5.1

Security fixes

Table 1. Security fixes
Issue key Vulnerability ID
INS-47644
INS-47642 CVE-2024-43788
INS-47636 CVE-2024-45590
INS-47633 CVE-2024-43800
INS-47615 CVE-2024-21529

Known limitations and workarounds for Guardium Insights v3.5.1

Table 2. Known limitations and workarounds for Guardium Insights v3.5.0

Known limitations and workarounds for Guardium Insights v3.5.0

Issue key Description
INS-29331 In rare cases, there are Db2® errors for services such as the reports and risk services. These may prevent report execution or risk event generation. When this occurs, these errors are seen in the logs for the related service:
SQLCODE=-1803, SQLSTATE=57056, SQLERRMC=NULLID.SYSSN200 0X5359534C564C3031, DRIVER=4.26.14
SQLCODE=-901, SQLSTATE=58004, SQLERRMC=Plan/Environment mismatch!, DRIVER=4.26.14

Workaround: See Db2 errors for reports and risk services.

Draft comment: jcalder@ca.ibm.com
Bug is marked as fixed in Jira only because it is documented here. I assume that this needs to stay in release notes for good.
  • INS-37007
  • INS-42808
After upgrading Guardium Insights from version 3.2.x to version 3.3.x and then to version 3.4.0, universal connector connections do not work due to a certificate error. Note that the workaround for this issue will be required as long as Guardium Insights version 3.3.x is in service.

Workaround: See Existing universal connector certificate does not work in a restored environment.

INS-37352 When there are very large amounts of data, the Data mart ingestion page displays this error:
Data mart unavailable Cannot load data mart statistics. Refresh the page to try again

Workaround: If the Data mart ingestion page displays this error, you can access the data mart ingestion information by opening the Data mart ingestion status report. This report includes data marts collected from both collectors and aggregators. To open the reports page, select Reports in the main menu. Open this menu by clicking the main menu icon (main menu)

INS-37724 When working with compliance milestones, you can Refine alerts with the Configure alert recipients action. When you choose this action and refine alerts, you can elect to send emails for actions. When you click the Send email to action and then click Invite users, the resulting landing page includes an Add users button that does not work.

Workaround: Go to the user management screen and add the user. Then return to the Refine alerts page to add the user to the list.

INS-39694 After modifying data retention settings, the new settings do not take effect until you restart the data retention pod.

Workaround: Restart the data retention pod after changing the settings.

INS-45613 When using the Azure Postgres universal connector, traffic is not captured and there is an error in azurepostgres_podlogs.

Workaround: Install the latest Azure PostgreSQL plug-in. To learn more, access the main documentation about the universal connectors.

Draft comment: jcalder@ca.ibm.com
The above content is draft for now. I have asked for a proper description/workaround in https://jira-ds.rtp.raleigh.ibm.com:8443/browse/INS-45613.
INS-46527 Links to product documentation from the welcome page are broken.

There is no workaround for this problem.

INS-47111 After upgrading to IBM Common Services version 4.6.5, there is an Unable to resolve host error in the cp-console route when logging.

This can happen when the default OpenID Connect (OIDC) client was not copied to Enterprise DB (EDB) after the upgrade. This is likely a timing issue which requires you to rerun the oidc-registration job and ensure the client is registered in Liberty, which uses EDB as its client and token store.

Workaround: Log in to the cluster by issuing these commands:
oc project $NAMESPACE
oc get job oidc-client-registration -o json | jq 'del(.spec.selector)' | jq 'del(.spec.template.metadata.labels)' | oc replace --force -f -

Resources

IBM Guardium Insights documentation: http://ibm.com/docs/SSWSZ5_3.x/

System requirements: Guardium Insights v3.5.x system requirements and prerequisites

IBM Security Learning Academy: https://www.securitylearningacademy.com