Data Masking

Owned by Gaurav
Last updated: Jul 27, 2023
3 min read

Overview 

This document helps users to understand the use of 'Obscure' field introduced on 'Column' tab of 'Database Schema' window and "Field" Tab of "Screen Configuration" window. This field is used to mask data to protect personally identifiable information, sensitive personal data etc. 

 

Product Version and dependency 

This feature is supported by 'Vienna Advantage Framework <4.2.32.0>'  

How to Use 

  1. Windows Level 

After installing the above module, "Obscure" field will be visible in "Column" tab of "Database Schema" window and "Field" Tab of "Screen Configuration" window. This field will be visible with string reference only.  

Obscure type is a dropdown which has the following four options: 

  1. Obscure Digits but Last 4 

  2. Obscure Digits but First/Last 4 

  3. Obscure Alphanumeric but last 4 

  4. Obscure Alphanumeric but first/last 4 

 

If a user chooses any of these options, then that field is treated as obscure field. Data in that field will be displayed in obscure format based on the option selected in Obscure field. If a field is marked as obscure, then that field is displayed as a read-only field and an icon appears with that field. If the user wants to see the original data or wants to edit the data, then the user has to click on that icon. When the user clicks that icon, the field will become editable and user can see and change the data.  

If the admin doesn't want to allow the users of a particular role to change or view the data, then admin can use "Role Data View" window. On this window, the admin can provide read-only access (or exclude) of field to a particular role. If any user login with that role then that icon with that field will not be displayed. So users cannot view and edit the data. 

 

  1. Reports Level 

When a column is marked as Obscure in column level, then the user who is fetching report has read-only access to that column, report will show obscure data for that column. 

In Vienna Advantage, most of the time report fetches data from views or temporary tables. These views or temporary tables must be present in "Database Schema" window and column in these tables should be marked as obscure (if want to display obscure data in report).  

 

When the user is using crystal reports, then for this user must create an entry of a temporary table or view in "Database Schema" window. In the "Report & Process" window, for crystal reports user type a query in the field. The table name and column name in the query are case sensitive from now. Cases of table name and column name of query must match with cases defined in table and column window.