Easily find issues by searching: #<Issue ID>
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Aqua Data Studio Data Masking lets you mask database table columns which contain sensitive information and protect Aqua Data Studio output from users who do not need to see the information. This is done by either substituting a new value of the same data type or nulling out the column in the result set. Aqua Data Studio users can select specific table columns to mask out before sharing information with colleagues.
The Aqua Data Studio Data Masking tool makes it convenient to select only the information that you want to be visible to others in your result set while still giving them access to a table's complete result set. This is done so that the data remains structurally workable but does not expose sensitive information.
For a Google BigQuery connection, the "SQL Version - Use Legacy SQL" option in the Advanced tab must be unchecked in order for Data Masking to work correctly.
The Data Masking UI has been created to make it easy to mask out specific tables and columns in a Database. All masking configuration changes are connection specific. If there are two different server connections there will be two different sets of rules. Changes made in one connection will not affect the other connection.
Note that while the Data Masking UI is being displayed, all other parts of Aqua Data Studio are not accessible. Thus, you must close the Data Masking UI in order to access other parts of Aqua Data Studio.
The Data Masking workspace has different options. The "Enable Data Masking" checkbox at the top lets the user enable or disable all data masking rules. The "Enable masked column header indicator" will display an icon in the result header throughout ADS to let the user know that the column that is displayed is also masked.
The toolbar menu in the Data Masking UI, gives users different options. Two buttons to select or unselect different columns at once, one to reverse selected columns and one to delete a specific row.
Note that only one rule can be deleted at a time.
Configure - To bring up the Data Masking rules dialog.
Configure Data Masking Rules - Users can add or delete rules.
In the Configure Data Masking Rules window, select which Database, Schema, Object Types, and Objects you want to mask out. First, select the database and schema location for the table(s) that you want to mask from the dropdowns. In the Objects Types window, select table and/or views. This will display all the tables and views for that database/schema combination in the Objects window. Selecting an object from the Objects window will display the columns for that object in the Columns section. Select which columns you want to mask and enter the Mask Value.
Editing values can only be done in the Configuration Data Masking rules window. Users can select the row in the main window, click Configure and the selected table will be highlighted in the Data Masking rules dialog so users can conveniently edit the values faster.
For MongoDB and Cassandra Databases - Schema column could appear empty.
Under the Mask Value column, you can select from the dropdown menu if you want it Not Masked, Null, Custom value or leave it Blank. Keep in mind that a blanked value only applies to String data types.
Please note that the Data Masking rules are not automatically updated, and may become invalid if the underlying table or view is altered. In order to avoid this potential issue, please finalize the database table and view designs before configuring data masking rules.
Table/View column can only be sorted manually in the main window, by clicking in the Table/View column title.
Data Masking can appear in different tools. Query Analyzer, Query Builder, Fluidshell, Aqua Command, Data Export, Aqua Script, and Edit Table Data.
Note that Data Masking is disabled for an Excel connection in Query Builder.