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.

Masking by column instead of result set .

Customer wants to mask columns that as been discovered such as sensitive data.

They can't afford to mask using the full result set due it's not 100% reliability and can give wrong results .

They know which columns and on which tables and the users that hasn't the right to see the data on a clear way.

  • Columns are : Name, surname, account number, emails, telephone number, National Identity Number.

  • Starting Database : Exadata X8 ( /

    • Others -> SQL Server 2016, SAP HANA v2

It should be considered as much as databases supported as possible.

  • Guest
  • Jul 28 2021
  • Not under consideration
  • Guest commented
    11 Jan 04:11pm

    @Rajesh .. Can you explain the rational behind the no consideration ?

  • Admin
    12 Dec, 2021 11:28pm

    We are not considering providing this capability at this time. We will have this in our backlog, will revisit this in a future review cycle.


    Product Management Team

    IBM Data Security / Guardium

  • Admin
    30 Jul, 2021 07:19pm

    Hello - thank you for your submission. We are looking into this request further, we will get back to you with our findings.


    Product Management Team

    IBM Data Security / Guardium

  • Guest commented
    29 Jul, 2021 09:00am

    This capability is really appreciated if included in Guardium. Masking sensitive data with such a little effort is something that is required in most of security teams responsible of data privacy.

  • Guest commented
    28 Jul, 2021 09:59am

    Customer is working on alternatives ways of masking the data.

  • Guest commented
    28 Jul, 2021 09:56am

    Customer has currently the v11.2 release.

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.