FieldShield GUI

Apply consistent data masking rules

With the IRI-Workbench GUI For FieldShield, you can also define and apply deterministic data masking rules for one or more data sources simultaneously. This protects columns in multiple tables (or files) with similar content in the same way, thereby preserving referential integrity.
 
For example, you can apply format-preserving encryption to all columns in a database containing a Social Security Number (which can be a key). For instance, if these column names can be matched by an expression with a pattern, the defined rule is applied.

The protection rule can be defined, stored, and reused in your data class or project rule library. By applying cross-table (or cross-file) rules, the need to repeatedly specify protective measures is avoided, a consistent appearance is achieved, and the links between tables are preserved; i.e., your joins will still work after masking. Restoration (e.g., decryption) can also be performed globally if needed.

Look at this article about the data class and rule library in the IRI Workbench and check out this article on masking data in a relational database to get a complete overview of how FieldShield data classification, search, and masking work together to to maintain referential integrity, by applying deterministic data masking rules such as format-preserving encryption to defined and recognized data classes.

Data class masking rules can also be automatically applied to multiple flat files in SMB directories. Look at this article to.

Article: Which data masking function should I use?

Check out the powerful data masking features you can typically apply in FieldShield or Voracity. Select the correct security method based on this criteria check: Read now