IBM Watson™ Discovery Service Ideas

We've moved...

You'll be redirected shortly, we've moved to our new idea portal: https://ibm-watson.ideas.aha.io

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit WDS-I-165 Data masking for ingested WDS documents.

Marking up or Masking certain fields based on identified entities (either from NLU or WKS) Merged

We have a use case where every document going into WDS index has to be masked for PII. We are planning to build a WKS model for name identification but a custom effort is required to mask the identified names and then store the documents in the index. This prevents us from using the out of the box NLU/WKS integration in WDS. So if we a masking layer on top of (Convert, Enrich, Normalize) then it will easy for the users to configure what has to be masked based on what.

  • DEEPAK SEKAR
  • Aug 29 2018
  • Anil Omanwar commented
    August 29, 2018 02:55

    Surely it will be very helpful in Various Domains. End user will love this feature.

  • DEEPAK SEKAR commented
    August 29, 2018 03:31

  • Graham Walker commented
    September 12, 2018 07:07

    If you were able to encrypt all customer data with a customer controlled master key, would you still need to mask these fields.  I work with a FSS customer here in Australia who are searching all text sent to Watson for PII data and tokenising everything that they find.  They have told me that if their data is encrypted with a master encryption key (BYO Key) that they control using something like Key Protect then they would not need to try to tokenise all the PII data.  

    See my idea that I submitted regarding a request for this ability to use a customer controlled master key.