Masking Data Fields in a Software Application is one of the methods that NanoToolkit IDentityJammer helps you obfuscate the sensitive data on the screen in an Ad-Hoc Fashion. Ad-Hoc Data Masking allows you to Block sensitive Data on the Web Application so that the Sensitive Data is protected against unintentional viewing. Typically sensitive data being protected by Data-Masking are fields that Contain a Person’s Identity or a Business’ Identity. Often times a person’s private data should be protected by Law; Congressional Acts Such as HPPA or PCI and government regulations call for securing Data related to people’s identity such that their privacy is not comprised.
IDentityJammer masks sensitive Data fields like social security, Address, First Name, Last Name, Date-Of Birth, Driver’s License Number, Insurance Member ID Number, Medicare ID, Medicaid ID, National ID and many Data Fields. IDentityJammer is also able to mask any kind Date, Currency, Rate, Integer or Rational Number. Masking Data is actually quite simple; IDentityJammer places asterisks where the Data used to be and remembers the original Data so that you can easily un-mask your obfuscated data-fields.
You can also choose to anonymize the Data Fields with classified Data instead of Masking the Data. Data Anonymization in Certain Situations can be the better choice than Data Masking. That’s because Anonymized Data gives you the appearance that the Data is actually real Data and not some arbitrary generated Names, Dates or Values.
Figure 1: The Original Clinic Patient Chief complaint Report.
Figure 2: The Masked Clinic Patient Chief complaint Report.
Figure 3: The Anonymized Clinic Patient Chief Complaint Report.