You can use Dynamic Data Masking to mask columns or block requests to a table that Informatica Secure@Source has identified as sensitive. From Secure@Source, you can export a CSV file that contains information about a particular data store. When you import the CSV file in Dynamic Data Masking, Dynamic Data Masking identifies which columns in the data store tables are protected by a security rule in Dynamic Data Masking. If a column is not protected by any security rule, you can apply a security rule at the column level or block requests to the table at the table level.
If you use Secure@Source in addition to Dynamic Data Masking, you can export details about a specific data store from Secure@Source as a CSV file. Export the
file from the
page in Secure@Source. The
file includes fields that the database scan in Secure@Source identified as sensitive. For more information about the
file, see the chapter "Overview Workspace" in the
Informatica Secure@Source User Guide
. If you try to import any CSV file other than the
file exported by Secure@Source, the import fails.
After you export the
file from Secure@Source, you can import it in Dynamic Data Masking. When you import the file, Dynamic Data Masking determines which columns in the data store are protected by a security rule already defined in Dynamic Data Masking. If all of the sensitive columns are protected by Dynamic Data Masking, you receive a message that "All the columns are protected."
For any unprotected columns, you can choose to apply a masking action or block all requests to the table. When you apply a masking action or block requests to the table, Dynamic Data Masking creates a rule based on the action you selected. If you choose the block action, Dynamic Data Masking creates a rule for every table name displayed in the table list. If you choose a masking action, Dynamic Data Masking creates a rule for every column name displayed in the table list. Dynamic Data Masking uses the From Clause Object matcher to match the column using the table name.