Data Masking Components: Address

{TOC}

" Address "

API Reference, CLR Reference (links)

Usage Instructions

Purpose

The purpose of the component is to randomly mask an element of address that includes street number. Often times referred as Address 1, this element usually consists of a street number, street direction, name, and suffix/abbreviation. An example would be 123 North Cherry Lane Street.

Algorithm

Random Substitution Algorithm

Description

Address component takes street address in one of the characters data types both ASCII and unicode (char, nchar, varchar, nvarchar, text, ntext) as an input and produces a street address in the same format as an output in the form of Street Number_Street Name_Street Predicate. The output of the address component is random. It does not guarantee uniqueness of the addresses that are produced although it produces more than a lotmillion combinations in creating addresses so that statistical variation of differentresults valuesis to sufficiently vary the entities.high.

API Reference, CLR Reference (links)

Usage Instructions:

1. Configure a source that contains the column with the element of address. TheA datasource incould thebe columnconnected may also includeto any otherdatabase, characterincluding thatbut willnot belimited treatedto SQL Server , Oracle, Sybase, mySQL, as well as a separator. file.
2. Drag and Drop "Masking GenericAddress" AlhaNumericdata Dynamic masking component, connect the source and the "Masking genericAddress" alphadata numericmasking component with the source'sdata precedenceflow constraint:path:
3. Now, the precedencedata constraintflow path (the blue arrow) passes proper meta-data and data to the Generic"Masking AlphaNumericAddress" data masking component. If you click on constraint,the data flow path, 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 ###**