Release Notes
Abstract
This technical note provides guidance for installing IBM Security Guardium Data Protection sniffer patch 11.0p4076, including any new features or enhancements, resolved or known issues, or notices associated with the patch.
Content
Patch information
- Patch file name: SqlGuard-11.0p4076_Snif_Apr_19_2024.tgz.enc.sig
- MD5 checksum: ff62a7efc333f424f0c79eec8644c33a
Finding the patch
Make the following selections to locate this patch for downlaod on the IBM Fix Central website:
Make the following selections to locate this patch for downlaod on the IBM Fix Central website:
- Product selector: IBM Security Guardium
- Installed version: 11.0
- Platform: All
- Click "Continue," select "Browse for fixes," and click "Continue" again.
- Enter the patch information in the "Filter fix details" field to locate the patch
For information about Guardium patch types and naming conventions, see the Understanding Guardium patch types and patch names support document.
Installation
Notes:
- This universal sniffer patch can be installed on all releases of Guardium 11.x
- This patch restarts the sniffer process.
Overiew:
- Download the patch and extract the compressed package outside the Guardium system.
- Pick a "quiet" or low-traffic time to install the patch on the Guardium system.
- Install patches in a top-down manner on all Guardium systems: start with the central manager, then aggregators, then the collectors. This sniffer patch must be installed across all the appliances such as the central manager, aggregators, and collectors.
For information about installing Guardium Data protection patches, see How to install patches in the Guardium documentation.
Enhancements
This patch provides the following enhancements:
| Issue key | Summary |
|---|---|
| GRD-78921 | Add ERROR option REQUEST_ERROR |
| GRD-76394 | Remove hardcoded limitation for MSSQL response |
| GRD-75315 | Token $(STATEMENT_KEY)$ |
New platforms supported
This patch adds support for the following platforms:
| Operating system | Database | Database version |
|---|---|---|
|
UNIX
|
Greenplum
|
7.0 |
| UNIX and Windows | MongoDB | 7.0.1 |
| UNIX and Windows | Postgres | 16 |
| UNIX | SAP HANA | 2 SPS7 |
Resolved issues
This patch resolves the following issues:
| Patch | Issue key | Summary | APAR |
|---|---|---|---|
| 11.0p4075 | -- | Patch 11.0p4075 on Fix Central | -- |
| 11.0p4076 | GRD-79295 | MSSQL: ALTER TABLE XXX ALTER COLUMN XXX DROP MASKED Caused Parser Error | DT260785 |
| GRD-78901 | Query Rewrite - Data masking works intermittently | DT261772 | |
| GRD-78783 | Create Database statement not being captured after upgrading to STAP 11.4.1.385 | DT260844 | |
| GRD-77823 | Report from Dec 5 for Oracle Bad_user 90 records | DT260856 | |
| GRD-77510 | Sybase segfaulting after ATAP Activation | GA18498 | |
| GRD-77504 | Unknown Sybase Error Code Logged by Guardium | DT258373 | |
| GRD-77485 | Sniffer Restart issue with p4071 new parser engine for Mongo for long sqls | DT257179 | |
| GRD-77368 | Full SQL not displaying actual values | DT260858 | |
| GRD-77234 | In real-time alert, some of "lastError" values are truncated | DT255096 | |
| GRD-77025 | Service name is not ignored in Ignore STAP session when configured within the tuple | DT261791 | |
| GRD-76972 | Block of code "DECLARE ... BEGIN ... END" always shows as Succeeded in the Full SQL entity ("GDM_CONSTRUCT_TEXT.SUCCESS=0) even if one query in the block fails | GA18497->DT249856 | |
| GRD-76418 | High CPU Causing Latency on Application - Mongo ATAP | DT260771 | |
| GRD-76163 | Failed Login in MYSQL not logged properly | DT257226 | |
| GRD-75818 | Missing DB-user for Sybase after applying v11.3_r114651 | -- | |
| GRD-75468 | K-TAP Request for 4.18.0-477.13.1.el8_8.s390x for V11.5 zlinux | -- | |
| GRD-75028 | S-GATE works inconsistently for some queries | GA18457 | |
| GRD-74437 | Core Dumps are generating on one of the DB server because memory leak in the code to process data from kerberos cache | DT260590 | |
| GRD-74169 | Not capturing traffic for Non-encrypted MySQL Server | DT257045 | |
| GRD-73424 | ORIGINAL_TIMEZONE is not properly calculated. | -- | |
| GRD-73223 | Missing DB User for some Sybase IQ sessions | GA18443 | |
| GRD-72455 | Server IP - Hostname mismatch | DT260795 | |
| GRD-72451 | Guardium data marts on Collector does not appear to be sending all the required data to SonarG. | DT261786 |
Known limitations
This patch contains the following known limitations:
| Issue key | Summary |
|---|---|
| GRD-80806 | Sessions are not closed for DB2_EXIT activities when global session key is enabled. Will be resolved in an upcoming patch. |
| GRD-80030 | Duplicated priority packets are not skipped on appliance side in case of failover when global session key is enabled. Will be resolved in an upcoming patch. |
| GRD-72455 | Session information lookup might be incorrect: Server IP - Hostname mismatch. Will be resolved in an upcoming patch. |
[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m3p000000PCTuAAO","label":"Platform\/Installation\/Deployment"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
21 June 2024
UID
ibm17145306