You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page.
Turn on more accessible mode
Turn off more accessible mode
Skip Ribbon Commands
Skip to main content
This page location is:
Big Data Management
Enterprise Data Catalog
Enterprise Data Lake
Enterprise Data Preparation
Cloud Application Integration
Cloud Data Integration
Cloud Customer 360
Cloud Data Wizard
Informatica Cloud for Amazon AWS
Informatica for Microsoft
Cloud Integration Hub
Cloud B2B Gateway
Cloud API Management
Complex Event Processing
Proactive Healthcare Decision Management
Real-Time Alert Manager
B2B Data Exchange
B2B Data Transformation
Data Integration Hub
Data Validation Option
Data Quality & Governance
Axon Data Governance
Data as a Service
Data Security Group (Formerly ILM)
Data Centric Security
Master Data Management
MDM – Relate 360
MDM Registry Edition
Product Information Management
MDM - Product 360
Ultra Messaging Options
Ultra Messaging Persistence Edition
Ultra Messaging Queuing Edition
Ultra Messaging Streaming Edition
Edge Data Streaming
PAM (Product Availability Matrices)
Informatica Expert Assistant
Velocity (Best Practices)
KB Home Page
Top Link Bar
FAQ: Can we use Dynamic Data Masking 9.9 with Informatica Secure@Source?
You can use Dynamic Data Masking (DDM) to mask columns or block requests to a table that Secure@Source (S@S) has identified as sensitive.
From S@S, export a CSV file that contains information about a particular data store.
When you import the CSV file in DDM, it identifies which columns in the data store tables are protected by a security rule in DDM. 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 S@S in addition to DDM, you can export details about a specific datastore from S@S as a CSV file.
file from the
page in S@S. The
file includes fields that the database scan in S@S identified as sensitive.
If you try to import any CSV file other than the
file exported by S@S corresponding to that data store, the import fails.
After you export the
file from S@S, import it in DDM.
When you import the file, DDM 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 DDM, we 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, DDM creates a rule based on the action selected.
If you choose the block action, DDM creates a rule for every table name displayed in the table list.
If you choose a masking action, DDM creates a rule for every column name displayed in the table list. DDM uses the From Clause Object matcher to match the column using the table name.
Dynamic Data Masking
Configuration; Product Feature
Administrator; Developer; Architect
Dynamic Data Masking 9.9; Secure@Source 5.0
Dynamic Data Masking
HOW TO: USE Secure@Source 5.0 with Dynamic Data Masking 9.9 (KB 577477)
Last Modified Date:
8/1/2019 12:18 AM
People who viewed this also viewed
Did this KB document help you?
This document resolved my issue
This document did not resolve my issue
This document helped but additional information was required to resolve my issue
What can we do to improve this information (2000 or fewer characters)
© 2016 Informatica All Rights Reserved