Masking watsonx.data assets in IBM watsonx.data intelligence

Last updated: Nov 13, 2025
Masking watsonx.data assets in IBM watsonx.data intelligence

You can use IBM watsonx.data intelligence to protect sensitive data in IBM watsonx.data.

When you work with sensitive data in watsonx.data, you can import it into IBM watsonx.data intelligence, and mask the data by using data protection rules. As a result, the data is available in the masked format also in watsonx.data.

Important: When the source data in watsonx.data changes, it might cause the masked data to be displayed in unmasked format in the catalog in IBM watsonx.data intelligence, and in watsonx.data. Data stewards are responsible for monitoring source data. If the source data changes, data protection rules must be reapplied on such data.

Prerequisites

Before you can start working with data protection rules on watsonx.data assets, you must authorize services instances to access each other:

  1. From Cloud Pak for Data as a Service, click Administration > Access (IAM), and under the Manage access category, open Authorizations.

  2. Click Create and authorize watsonx.data to access IBM watsonx.data intelligence:

    • Source: select watsonx.data.
    • Target: select IBM watsonx.data intelligence.
    • Role: select the Watsonx.data Service Access (For Service to Service Authorization Only) for IKC role.

    Click Authorize.

  3. Click Create and authorize IBM watsonx.data intelligence to access watsonx.data:

    • Source: select IBM watsonx.data intelligence.
    • Target: select watsonx.data.
    • Role: select the DataAccess role.

    Click Authorize.

Masking data

To mask watsonx.data in IBM watsonx.data intelligence, follow these steps:

  1. Create a catalog and select the Enforce data protection and data location rules.
  2. In the new catalog, add the connection to watsonx.data. For connection details, see IBM watsonx.data Presto connection.
  3. In the new catalog, add assets from watsonx.data by using the Add to catalog > Connected asset option.
  4. Mask the imported data with data protection rules. For details, see Data protection rules.

Learn more