Data Masking Components: Address Dynamic

{TOC}

"Address Dynamic "

API Reference, CLR Reference (links)

Usage Instructions:

Purpose

The purpose of the component is to mask suchan valueselement of address that includes street number so that the referential integrity is sustained across the different data structures. Often times referred as AccountAddress or1, Patientthis Numberselement thatusually often consistconsists of thea combinationstreet ofnumber, Alphastreet direction, name, and Numericsuffix/abbreviation. charactersAn andexample arewould notbe formed123 byNorth aCherry specificLane rule.Street.

Algorithm

Variation of Random Character PermutationSubstitution Algorithm

Description

Masking Address Dynamic component replacestakes lettersstreet withaddress letters,in whileone maintaining capitalization,of the characters data types, both ASCII and replacesunicode numbers(char, withnchar, numbers.varchar, Itnvarchar, retainstext, ntext) as an input and produces a street address in the non-alphanumericsame characters, suchformat as dashes,an slashes,output dots and comas, exactly atin the positionform atof Street whichNumber_Street theName_Street non-alphanumeric characters presented themselves at the source value. It currently only replaces characters from alphabets that use English characters.Predicate. The component willguarantees replaceconsistent stringsrepeated basedtransformation onof lettersvalues. onlyIt withdoes letternot stringsguarantee anduniqueness stringsof basedthe onaddresses numericthat characters,are onlyproduced withas numerican characters.output Forbut example,uses "Abc"more willthan becomea "Zyx"million andcombinations "123"in willcreating becomeaddresses "987"so afterthe componentstatistical variation execution.of the resulting values is high.

API Reference, CLR Reference (links)

Usage Instructions:Instructions

1. Configure a source that contains the column with alphabetical and numeric characters. The data in the columnelement mayof alsoaddress. includeA source could be connected to 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 Dynamic" data masking component. If you click on constraint,the data flow path, you will see:
4. Now that the metadata for the GAN"Masking Address Dynamic" data masking component exists, and values are passed into the data masking component,it, please open the component editor:
5. In the second tab,tab of the component editor, "Input Columns", there are available input columns. Please check-markchoose only one column, the onecolumns that you will be masking with Genericthe Alpharandom Numericaddress algorithm:substitution algorithm. You could either check-mark it or choose from the drop-down of the available columns:
6. ThisPlease, willnotice createthat anyou extracan columnmask at the same time two or more columns with the prefixsame “Masked_”.algorithm:
7. Choosing the column(s) will create a new column(s) with the prefix “Masked_field”. This is the column that will hold an obfuscated value(s) of the same data type, code page and length:
8. Create a connection manager for the destination and configure sourcedestination componentcomponent. forRead the destination.example instructions on how to configure different SSIS connection managers and destination components here. In the connection manager, in the tab “Mappings”, specify that you want newly created Field_Masked"Masked_field" 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.9. Now, all the configurations are complete for the valid values. You can run the package with the Generic AlphaNumeric DynamicAddress Data Masking component, and see the results of data masking:

Error Handling

9.10. 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 precedencedata constraint.flow ( the red arrow). One needs to create an error destination connection and connect the 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.11. 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.12.The It is our suggestiondata that did not confirm to the components' rules can be fixed in production and/or processed with the Generic Alpha Numeric component one should not process erroneous data without further analysis at all.component.

Download Example ###**