Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Categories Event Streams
Created by Guest
Created on Nov 5, 2024

Automated encryption of sensible data, directed by the schema registry

Hello,

Kafka events can sometimes carry sensitive data that is either subjected to the RGPD, banking security or of hight confidentiality.

We would like to have the possibility to add flags in schemas for sensible fields, or flag the entirety of an event schema as sensible, thus enforcing automated encryption of the sensible part of the data when the event is written by the consumer, and automated decryption by the allowed consumers and only them.

The goal is to prevent possible leaks of sensible data from users with admin/display rights that could examine the content of events directly on the kafka brokers.

Thank you for considering this suggestion if you can

Idea priority Low