Release Notes
Abstract
This technical note provides guidance for installing IBM Guardium Data Protection Windows Agents 12.0.5.366, including any new features or enhancements, resolved or known issues, or notices associated with the patch.
Content
Patch information
| Product: | IBM Guardium |
|---|---|
| Release version: | Guardium 12.0 Windows Software TAP (S-TAP) |
| Completion date: | 31 October 2025 |
Fix IDs
Guardium_12.0.5.366_S-TAP_Windows |
Finding the patch
- Select the following options to download this patch on the IBM Fix Central website and click Continue.
- Product selector: IBM Security Guardium
- Installed Version: 12.0
- Platform: Windows
- On the "Identify fixes" page, select Browse for fixes and click Continue.
- On the "Select fixes" page, select Database Agent (STAP, GIM and CAS). Then, enter the patch information in the Filter fix details field to locate the patch.
Notes
- A fresh install of Guardium 12.0 does not require a reboot.
- When you upgrade between versions, you must reboot the database server to update the NmpProxy driver. If there are no issues with your current NmpProxy functionality, you can delay the reboot until the next maintenance cycle. No fixes will be applied to the NmpProxy driver until a server reboot is completed.
- IBM strongly recommends that you do not use the following builds as they contain instabilities that can lead to system failure. Uninstall these builds and reboot before you install S-TAP 12.0. For all other builds, you can upgrade as usual.
- 11.4.0.168 through 11.4.0.204
- 11.3.0.257 through 11.3.0.287
Attention
Database instance stop and server reboot required for patch upgrade
When you upgrade to Windows S-TAP 12.0.5.366, you must reboot the database server to update the NmpProxy driver. To successfully install this patch, you must complete the following steps:
- Stop all database instances.
- Upgrade Windows S-TAP to version 12.0.5.366.
- Reboot your database server immediately after you upgrade Windows S-TAP.
- Start your database instances.
New support and functionality
Microsoft Windows Server 2025
Support added for Windows Server 2025.
New features and enhancements
Restricting traffic base on IE process name
S-TAP can now filter for Transmission Control Protocol (TCP) traffic directed to the database server processes specified in the inspection engines to reduce traffic noise. The following parameters were added to control this new functionality.
WFP_PROCESS_RESOLVE_MODE
Description: This parameter dictates how S-TAP handles traffic from non-SQL Server sources on SQL Server ports.
Description: This parameter dictates how S-TAP handles traffic from non-SQL Server sources on SQL Server ports.
Default value: 0
Possible values:
0 - Traffic from non-SQL Server programs using SQL Server ports is sent to the S-TAP and the collector.
Possible values:
0 - Traffic from non-SQL Server programs using SQL Server ports is sent to the S-TAP and the collector.
1 - Traffic from non-SQL Server programs using SQL Server ports is ignored.
2 - Traffic from non-SQL Server programs using SQL Server ports is passed if it reaches one of the two resolve limits, otherwise it is ignored.
WFP_PROCESS_RESOLVE_LIMIT
Description: This is the limit in KB of how much traffic is buffered per connection while attempting to resolve the server process name. If the limit is reached, traffic is either dropped or passed depending on the mode.
Default value: 2048
Value range: 1 - 20480
Default value: 2048
Value range: 1 - 20480
WFP_PROCESS_RESOLVE_TOTAL_LIMIT
Description: This is the limit in MB of how much traffic is buffered system-wide while attempting to resolve server process.
Description: This is the limit in MB of how much traffic is buffered system-wide while attempting to resolve server process.
These new parameters can be modified by using Windows GIM 12.0.0.295 or later (see release note).
Allowing database sessions to make progress when all collectors are down
In protocol 8, when in a situation where all collectors for a S-TAP are down, and the firewall or query rewrite is active, S-TAP must immediately pass packets to keep database sessions active if the default verdict is pass, or drop sessions if the default verdict is Drop. The following parameter was added for S-TAP to allow database sessions to make progress when all collectors down.
VERDICT_RESUME_DELAY
Description: This parameter allows database sessions to make progress when all collectors down. The value is the number of seconds the S-TAP will delay sending verdict requests to the collector after a failover. During this time, S-TAP acknowledges the verdicts locally. After the time period expires, the S-TAP resumes sending verdict requests to the collector.
Default value: 30
Value range: 0-300
Resolved issues
Patch | Issue key | Summary | Known issue (APAR) |
|---|---|---|---|
12.0.0.259 | See release note for Windows S-TAP 12.0.0.259 | ||
| 12.0.5.366 | GRD-82303 | Access to shared data structures were synchronized, and data items that were allocated and retained during session execution were deallocated when the session ended. | DT419137 |
GRD-89175 | Fixed session correlation and Kerberos delivery timeouts. | DT438267 | |
GRD-91304 GRD-100202 | Fixed potential instability in Windows S-TAP related to processing non-database TCP traffic. | ||
| GRD-91681 | Fixed possible failures with capturing TCP traffic in S-TAP | DT421661 | |
GRD-92152 | Fixed S-TAP service instability at startup. | DT426016 | |
GRD-92349 | Fixed an issue related to possible termination of sessions when Firewall S-Gate is enabled. | DT426053 | |
GRD-93363 | Fixed instability in S-TAP protocol 7 related to automatic IP correction after S-TAP startup. | ||
GRD-94302 | Fixed instability in Microsoft SQL Server caused by Correlator DLL of Windows S-TAP. | DT437922 | |
GRD-97837 | Windows S-TAP now uses OpenSSL 3.5. | ||
GRD-98934 | MustGather: Host name and Windows operating system (OS) patch list added to summary.txt | ||
GRD-99833 GRD-99842 | Fixed Microsoft SQL Server instability caused by S-TAP related to correlator software, which is triggered when using multiple active result sets (MARS) on encrypted database connections. For more information, see Guardium Windows S-TAP 12.1.0.162, 12.0.0.293, and 11.5.0.437 might cause Microsoft SQL Server instability when using MARS on an encrypted database connection. | DT438501 | |
GRD-101002 GRD-102219 | Fixed instability in Microsoft SQL Server caused by S-TAP when connecting to Microsoft SQL Server though IP. For more information, see Guardium Windows S-TAP 12.1.0.195, 12.0.1.295, and 11.5.1.437 might cause Microsoft SQL Server instability when using Kerberos authentication. | DT442106 | |
GRD-101025 | Fixed instability in Windows S-TAP caused by data packets exceeding 64K. | DT442121 | |
GRD-101938 | Fixed instability in Windows OS caused by Windows S-TAP WFP driver. For more information, see Guardium Windows S-TAP 12.1 might cause Windows OS server instability with non-database traffic using duplicate IPs and ports. | DT443493 | |
GRD-103773 | Removed old registry entries after upgrading from Windows S-TAP 9. | DT454710 | |
GRD-107904 | Fixed instability in Windows OS due to unintended processing of non-database traffic. For more information, see Guardium Windows S-TAP 12.1.19.195, 12.0.1.295, or 11.5.1.437 might cause Windows OS server instability with S-TAP picking non-database traffic. | ||
GRD-109007 | Fixed an issue in S-TAP Named Pipes proxy driver potentially causing Remote Procedure Calls failures. For more information see Guardium Windows S-TAP 12.1.19.195, 12.0.1.295, 11.5.10.478 might cause Windows OS server unavailability with RDP access. | DT454370 |
Installers with MD5Sums
| MD5Sum | File Name |
|---|---|
a8a8bf1fc91dafbe3c6eba92b3dcc665 | Windows-STAP-V12.0.5.366.zip |
| 2e3a3bf0273dc94edf36fa5ed259897a | conf.reload.WINSTAP |
| 79d393a43839a965f2de9bc8d4a8eb3b | guard-WINSTAP-12.0_r120005366_1-x86_x64.gim |
| 6163fa5adc17eb47e568fface3540c49 | guard-WINSTAP-guardium_12.0_r120005366_1-Windows-Server-Windows-x86_x64.exe.signed |
Related Guardium updates
- Guardium Data Protection Windows FDEC for NAS 12.0.5.366 (see release note)
- Guardium Data Protection Windows FDEC for SharePoint 12.0.5.366 (see release note)
- Guardium Data Protection Windows FAM for NAS 12.0.5.366 (see release note)
- Guardium Data Protection Windows FAM for SharePoint 12.0.5.366 (see release note)
- Guardium Data Protection Windows GIM 12.0.5.366 (see release note)
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m3p000000PCTuAAO","label":"Platform\/Installation\/Deployment"},{"code":"a8m0z000000Gp0IAAS","label":"STAP"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"12.0.0"}]
Was this topic helpful?
Document Information
Modified date:
17 November 2025
UID
ibm17240218