Release of Guardium Data Protection patch 12.0p1064

Content

• Patch file name: SqlGuard-12.0p1064.tgz.enc.sig
• MD5 checksum: c570d58f7af1cd9b94a751923ffc77dc

Note: This patch is intended only for Guardium Data Protection customers who upgraded environments to Guardium Patch Update (GPU) 12.0p240 prior to its removal from Fix Central and Passport Advantage. Customers who upgraded to the replacement GPU 12.0p7240 should not install patch 12.0p1064.  For more information, see Remote syslog issues after upgrading to Guardium appliance patch 12.0p240.

• Guardium Patch Update (GPU) 12.0p240 
• The latest Guardium Data Protection health check patch 12.0p9997 (see release notes)

• This ad hoc patch restarts the rsyslog service, and nanny, classifier, and Tomcat processes.
• Do not reboot the appliance while the patch install is in progress. Contact IBM Support if there is an issue with patch installation.
• When changing the password of CLI and guardcli users in the Guardium command line interface, a password strength warning appears even when strong passwords are not enabled. To remove the strong password checks, execute the CLI command store user strong_password disable.

1. Download the patch and extract the compressed package outside the Guardium system.
2. Review the latest version of the patch release notes just before you install the patch.
3. Pick a "quiet" or low-traffic time to install the patch on the Guardium system.
4. Install patches in a top-down manner on all Guardium systems: start with the central manager, then aggregators, then the collectors.

Identify the patch installation status of managed units from the central manager       
Check which managed unit appliances you need to apply patch 12.0p1064 by using the following central manager user interface (UI) or command-line interface (CLI) instructions to verify whether GPU 12.0p240 was installed.

• From the Guardium UI 
  • Option 1: Click Manage > Central Management > Central Management to open the "Central management" page. Filter or sort the Version column to identify which units are on version 12.2.4 and check whether the corresponding entry in the Last Patch column indicates that 12.0p240 is installed.
  • Option 2: Click Manage > Central Management > Central Management > Actions > Patch management to open the "Patch management" page. Filter or sort the Guardium version column to identify which units are on version 12.2.4 and check whether the corresponding entry in the Patch status column indicates that patch 12.0p240 is installed. 
  • Option 3: Go to My Dashboards and create a new dashboard or select an existing one. From that dashboard, click Add Report. Filter and select "Latest patch by type-Distributed (Immediate)” from the list, and click Close. In the report, click Run Distributed Report to see which units have patch 12.0p240 installed.

Note: On Guardium enterprise hub, only Option 2 is available.

• From the Guardium CLI  
  SSH into the central manager CLI as cli user and run the following command: grdapi show_patch_status api_target_host=all_managed_units This command queries all registered managed units and returns a list of installed patches per unit. The api_target_host parameter is what routes the grdapi call to the managed units instead of running it locally on the central manager. 
  • If you want to target a specific managed unit by IP or hostname, run the following command: grdapi show_patch_status api_target_host=<MU_IP_or_hostname>
  • If the show_patch_status command is unavailable on your appliance version, run the following alternative command: grdapi list_patch api_target_host=all_managed_units
  • If you're unsure of which exact patch-related commands your appliance version exposes, run the following command to enumerate available patch commands on your appliance: grdapi commands | grep -i patch 

Note: To run these commands, you must be an admin or have a role with patch management permissions.