Release notes - Guardium Data Security Center 3.6.0
IBM Guardium Data Security Center protects your data from current and emerging risks, including AI threats and cryptographic attacks, through unified security controls. The offering helps you manage the full data security lifecycle, from discovery to remediation, across all your data environments. It allows you to break down organizational silos and empowers security teams to collaborate across the organization through integrated workflows, a common view of data assets, centralized compliance policies and an open ecosystem.
The modules of IBM Guardium Data Security Center include:
- IBM Guardium Data Compliance
- Data Compliance Programmatically simplify data regulation needs, enhance visibility, and streamline monitoring.
- IBM Guardium Data Detection and Response
- DDR Safeguard your data with ready-to-use integrations that enable your SOC to locate signals in the noise.
- IBM Guardium Quantum Safe
- Quantum Safe Monitor your enterprise’s cryptography use, uncover cryptographic vulnerabilities, and prioritize remediation to secure your data from both conventional and quantum-enabled risks.
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/tree/master/repo/case/ibm-guardium-data-security-center
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
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:
- Prepare for installing IBM Guardium Data Security Center
- Install Guardium Data Security Center
- Upgrade process
- 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.
Version 3.6
- Check cluster and product health with the Guardium Data Security Center command-line utility
- Use the
guardcenter-cli
command-line utility to help ensure that clusters are functioning at an optimal level. Using this utility can help you proactively identify any issues within the cluster, and maintain and boost productivity.For more information, see System requirements for the Guardium Data Security Center command-line interface utility, Installing the Guardium Data Security Center command-line interface utility, and Check cluster and platform health by using Guardium Data Security Center CLI commands.
- Steaming analytics outlier support
- Steaming analytics outlier support is added to detect the potential emerging risk events by
detecting the outliers from the streaming data. These changes have been made to detect the emerging
risk in near real-time:
- An Emerging risk events card is added in the Overview dashboard page, to view all the emerging risks at a glance.
- On the Risk Events page, a Dashboard tab is added, which displays the emerging findings, excess activities, and other findings. For more information, see Viewing and managing Risk Events.
- Emerging risk error report is added. For more information, see Predefined reports, tags, and data points.
Bug fixes in Guardium Data Security Center 3.6.0
Issue key | Description |
---|---|
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 did not work. |
INS-39694 | 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 | 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 | 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
Issue key | Description |
---|---|
INS-49682 | 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 | 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 | 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 | 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. |
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 v3.6.x system requirements and prerequisites
IBM Security Learning Academy: https://www.securitylearningacademy.com