IBM Security Guardium Ideas Portal

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Post an Idea

To post a new idea - click on the "Add a new idea" button and select the appropriate capability area this idea relates to. Do provide requested information to allow us to get a better understanding of your request. If 'Guardium Data Protection' capability is selected, you will be prompted to select the category/product the idea relates to. If you are not sure of the category/product your idea would fall under, then select 'IBM Guardium Other' in the drop down list and proceed from there.

Please note: The purpose of the Ideas Portal is to tap the creativity of the Guardium Data Protection community so that we can enhance the product for everyone! If you need to report a defect or get help, please use our normal support channel. Click here to open a support ticket.

For IBMers, click here to submit an idea on behalf of a customer, if the customer prefers to keep their use case and idea private.

enhance Multi Master code upgrade (FP) process to not cause 100% downtime of all key providers

Enhance Multi Master code upgrade (FP) process to not cause 100% downtime of all key providers.

Currently it is required per Fixpack installation instruction to stop perform the following actions which causes 100% of the key server infrastructure to be down and not capable of service keys to DASD or tape or any other KMIP client.

  1. Stop WebSphere Liberty on all the master servers, in any sequence.

  2. Stop Agent on all the master servers, in any sequence.

  3. update the servers in the following sequence:

    1. Primary master server

    2. Principal standby master server

    3. Auxiliary standby master servers

    4. Non-HADR master servers

  4. start GKLM servers again

Above sequence is causing a 100% outage of the key server infrastructure .

Taking into account that the use-cases that mandaory required Multi-Master deployments vs Replication are almost only Enterprise DASD with IBM Z (e.g. TCT =Transparent Cloud Tiering and Encryption of Data-In-Flight =EDIF / Fibre Channel Endpoint Security = FCES) we are talking here about 5x9 HA components with extreme limited downtime. Hard to argue to stop a 4 Node GKLM Multi-Master cluster and not beeing able to serve keys for a significant amount of time, potentially muliple times a year with planned FP and unplanned fixes like patches for security exposures.

More customers are opting in for Multi-Master now even they do not yet need KMIP and MM with DS8K because they are planning to use TCT / FCES in the near future.

In case a MM deployment is shared with tape libraries of any kind, TS7700 VTS, TS4500, TS3500, TS4300 and others, to name only IBMs tape libraries, the impact of a key server and its standby server is significantly higher than for DASD (most DASD only need the key to unlock Ranks, Arrays, pools during power on reset but will trigger alerts / IBM call homes).

For tape drives, an unresposive keyserver means that during that time, all tape mounts of encrypted tapes and scratch tapes will fail. This is tru for scratch mounts, write appends but more significantly for restore / tape recall operations.

  • Guest
  • Mar 4 2022
  • Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.