Data Masking Components: Load Dictionary

{TOC}

"LoadSSIS Dictionary"Load Dictionary Component

API Reference, CLR Reference (links)

Usage Instructions:

Purpose

The purpose of the Load Dictionary component is to maskcreate a custom dictionary of values for the later use in Dictionary Substitution component. If the data schema includes certain elements that could not be masked using substitution components with pre-packaged data sets such values as Accountnames or Patientcompanies, Numbersthan thatthis oftenparticular consistcomponent allows to create a set of (key,value) pairs in memory. Dictionary Substitution component picks up the combinationvalues and replaces them with the substitution algorithm. Examples might include creating sets of Alpha"languages" andfrom Numericthe characterslanguage andtable, areor not"brands" formedfrom bythe abrand specifictable rule.in the database, etc.

Algorithm

VariationWhile none of Randomthe Characterdata Permutationmasking Algorithmalgorithms are applicable, Load Dictionary simply retrieves a data set from the indicated source and makes it available via Object type variable.

Description

Load Dictionary component replacesretrieves lettersthe with letters, while maintaining capitalization,key and replacesthe numberscorresponding withdata numbers.field Itvalues retainsfrom the non-alphanumericdata characters,source, suchbe asit dashes,a slashes,table dotsin a database or a file, and comas, exactly atplaces the positionset atof which(key, thevalue non-alphanumericpair) charactersinto presentedpredefined themselvesObject atVariable theto sourcebe value.later Itused currentlyin onlyDictionary replacesSubstitution characters from alphabets that use English characters. The component will replace strings based on letters only with letter strings and strings based on numeric characters, only with numeric characters. For example, "Abc" will become "Zyx" and "123" will become "987" after component execution.Component.

API Reference, CLR Reference (links)

Usage Instructions:

1. Configure a source that contains the id column with alphabetical and numeric characters. The data in the column mayyou alsowant includeto any other character that will be treated ascreate a separator.custom data set from.
2. Drag and Drop GenericLoad AlhaNumericDictionary Dynamic data masking component, and connect the source and the genericLoad alphaDictionary numeric component with the source's precedence constraint:component.
3. Now, the precedence constraint (the blue arrow) passes proper meta-data to the Generic AlphaNumeric component. If you click on constraint, you will see:
4. Now that the metadata for the GAN exists, and values are passed into the data masking component, please open the component editor:
5. In the second tab, there are input columns. Please check-mark only one column, the one that you will be masking with Generic Alpha Numeric algorithm:
6. This will create an extra column with the prefix “Masked_”.
7. Create a connection manager for the destination and configure source component for the destination. In the connection manager, in the tab “Mappings”, specify that you want newly created Field_Masked to be a field replacing the original value. For that, just click on the available input columns, choose the masked value, and map to the “Available Destination Columns”
8. Now, all the configurations are complete for the valid values. You can run the package with the Generic AlphaNumeric Dynamic Data Masking component, and see the results of data masking:

Error Handling

9. If, however, there are invalid values in the package's source, one would need to configure error handling. Invalid values are those that are not conforming to the rules of the entity. To handle invalid values, each data masking component has error handling precedence constraint. One needs to create error destination connection and connect red arrow (error handling constraint) with this destination. As the connection is made, one needs to configure the state of failure: “Fail”,”Ignore” or “Redirect”.
10. It is recommended that one re-directs the output into the error destination, so that later one be able to analyze and process data for quality purposes. The Generic Alpha Numeric components errors are the only ones not recommended for further processing as it is truly hard to break their format.
11. It is our suggestion that with Generic Alpha Numeric component one should not process erroneous data without further analysis at all.

Download Example ###**