Release notes - Guardium Data Security Center 3.6.0

Release notes contain information to help you get started with Guardium® products, such as installation instructions, upgrade information, known issues, resolved issues, and security fixes.

Contents

Download Guardium Data Security Center 3.6.0

Guardium Data Security Center 3.6.0 can be downloaded as an archive file (ibm-guardium-data-security-center-2.6.0.tgz) from: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-guardium-data-security-center/index.yaml

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.

Install Guardium Data Security Center 3.6.0

Important: When upgrading to version 3.6.0 or patching to 3.6.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 Data Security Center, review the system requirements.

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

Important: Before upgrading to Guardium Data Security Center, ensure that all data migration from previous versions has taken place. In addition, you must upgrade Guardium Data Protection to one of these patches before upgrading to enable v5 data ingestion:
  • For Guardium Data Protection 11.4, upgrade to patch 11.0p490.
  • For Guardium Data Protection 11.5, upgrade to patch 11.0p535.
  • For Guardium Data Protection 12.0, upgrade to patch 12.0p10.

Bug fixes in Guardium Data Security Center 3.6.0

Table 1. Bug fixes
Issue key Description
INS-37724
Draft comment: jcalder@ca.ibm.com
link to bug
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 did not work.
INS-39694
Draft comment: jcalder@ca.ibm.com
link to bug
The data-retention pod did not launch the data-retention(purge/archive) logic if its dependencies did not exist. The pod would remain off after the dependencies did get created.
INS-44090
Draft comment: jcalder@ca.ibm.com
link to bug
When too many data marts were ingested at once, the ssh-service stopped sending notifications. This lead to data marts appearing with an awaiting for data state.
INS-48686
Draft comment: jcalder@ca.ibm.com
link to bug
The gi-lab-tenant-create pod exposed the cpadmin credentials within the log files.

Known limitations and workarounds for Guardium Data Security Center 3.6.0

Table 2. Known limitations and workarounds for Guardium Data Security Center 3.6.0

Known limitations and workarounds for Guardium Data Security Center 3.6.0

Issue key Description
INS-49682
Draft comment: jcalder@ca.ibm.com
link to bug
After upgrading to Guardium Data Security Center 3.6, mustgather does not work.

Workaround: This typically occurs when Db2® is running long queries on assets. If you end these queries, mustgather should complete.

INS-49680
Draft comment: jcalder@ca.ibm.com
link to bug
After adding a user in the User management page, the user is added but does not appear in the list of users.

Workaround: Refresh the browser page to have the user display in the list of users.

INS-49598
Draft comment: jcalder@ca.ibm.com
link to bug
Data mart processor log includes Expected tokens may include: \"<ext_tab_element_list>\". errors.

Workaround: There is no workaround required for this issue. Data mart ingestion will complete as expected.

After changing the name format of the CSV file, attempts to retry data ingestion fail.

Workaround: Importing the data again may resolve the issue.

INS-49266
Draft comment: jcalder@ca.ibm.com
link to bug
After upgrading several times from previous versions to Guardium Data Security Center 3.6, the push and pull mode of export data mart bundles from Guardium Data Protection fail.
Draft comment: jcalder@ca.ibm.com
Is there a workaround for this?

Resources

Product page: https://www.ibm.com/products/guardium-data-security-center

IBM Guardium Data Security Center documentation: Guardium Data Security Center overview

Guardium Data Security Center system requirements and prerequisites

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