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.

Supercedes RFE 137574: Key governance: Need to prevent client app from performing operations on shared keys

Key governance: Need to prevent client app from performing operations on shared keys: If a shared key is created at the domain level by an Admin using the DSM UI, there's nothing preventing a client app from using the API from creating/changing/rotating keys in that same domain.

Recall that customer is using shared keys for each data type (e.g. one for SSN/SIN, one for credit card #, one for government id) so that performing encryption or decryption using any of the access methods (Teradata UDFs, Hive UDFs, BDT, Java library API) will consistently encrypt/decrypt that data type regardless of where it's stored in Teradata and Hortonworks. It is therefore critical to prevent unauthorized activities against these key. This is a SHOWSTOPPER governance issue.

Desired enhancement is to provide the ability in the DSM to prevent a client app from using the API to create/change/delete keys in that domain.

As a short term fix, there is a suggestion to add a flag in the DSM that indicates if the domain will be shared or not (and if so, whether to prevent the APIs from performing operations in that domain). Longer term the recommendation is to provide an ACL (role level control - ideally leveraging the LDAP) in the DSM that allows for more granular control of who is allowed to make changes via the API.

Note that Thales Engineering has created these 2 Jira activities:
PMSJ-2572 (emergency fix to prevent a client app from performing operations in the shared key domain)

PMSJ-2576 (near term enhancement to provide role level granular control of who is allowed to make changes to shared keys via the API)

Note that this RFE supercedes RFE 137574

  • Guest
  • Jan 26 2021
  • Delivered
  • Admin
    Michael Saldarriaga commented
    27 Apr 02:30pm

    Comment from the software provider: Granular role level control that can be used to prevent client applications from making changes in keys and rotating keys is already available in CipherTrust Manager (GDE 5.0). With DSM (GDE 4.0) being sunset (end of support: June 2024), availability of this functionality already available on CipherTrust Manager is the only option we can propose for this RFE.

  • Admin
    Michael Saldarriaga commented
    27 Apr 02:28pm

    This functionality has been delivered on GDEv5. Since Thales plans to sunset GDEv4 in 2024, they have no plans to add it to the DSM.

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.