DataSunrise Dynamic Data Masking for IBM DB2

IBM DB2 data masking tool by DataSunrise allows you to protect organizations' data stored in IBM DB2 database from insider attacks and unintentional data leaks. It deters the misuse of data in production databases. It transforms original data to hide sensitive information but keeps it looking realistically. With data masking you can easily limit your critical business data exposure to non-privileged users.

Tech Info

IBM DB2 data masking tool by DataSunrise is an efficient method of preventing sensitive information exposure when giving database access to third-party. There are a lot of situations when organizations need to share data from their production databases with third party. Here are some examples:

  • A certain organization hires outsourced IT specialists to customize its business system or perform database testing, upgrade etc.
  • Healthcare company provides medical researchers with information on clinical trials.
  • Retail company shares sales information with market researchers.

The point is that in most cases third-party specialists don’t need real data the database contains. An environment mimicking a real production database is enough. The best way to protect sensitive data while transferring it to third-party is to replace it with some neutral data. And the most efficient way to do this is masking.

The important point is that masked data should be consistent enough to support proper functioning of the third party’s application. In simple words, the main purpose of masking is to make sensitive data useless for evil-doers while keeping it useful for the ones that should receive it.

Sometimes in such situations static masking is used. It is about providing the third party with a stand-alone copy of the real database containing some neutral data instead of sensitive data. While this method is reliable, it could be pricey and time-consuming.

That’s why in most cases dynamic data masking is preferable. Unlike static data masking, dynamic data masking is about obfuscating sensitive data on-the-fly, while transferring it to third party. In this case, actual database contents remain intact and only database output is obfuscated.

This is how it works

IBM DB2 data masking tool by DataSunrise is deployed as a proxy between clients (those third-party specialists) and your IBM DB2 database. Clients contact production database through DataSunrise proxy only (any direct access to database is disabled).

DataSunrise intercepts client query, changes it according to existing security policies and redirects modified (“masked”) query to the database. Having received “masked” query, the database outputs fake (obfuscated) data instead of real values originally requested by the client. Since no real data leaves the database, this method of data obfuscation is very reliable.

And this is how it looks like

Netezza tableFor example, here we have a IBM DB2 table which simulates a list of customers including addresses, emails and credit card numbers. Before exporting this list to a third-party system, we need to obfuscate customers’ personal data.

To do this, it is necessary to create some masking rules. Along with general-purpose masking methods, DataSunrise provides obfuscation algorithms for emails and credit card numbers. So, we’ve created some masking rules to obfuscate data in columns that contain customers' addresses, ZIP codes and credit card numbers. Let’s assume that leaving their names, order numbers and email addresses unmasked is acceptable.

Netezza table masked

And here how the table looks like after the masking is applied. As you can see, data in specified columns were obfuscated and thus, it became senseless for potential wrong-doer.

Masking internals

Now let's see how masking looks like in SQL.

Here's the original client query:


And SQL query the database gets after masking is applied:

       SYSTEM.ADMIN.TEST_TABLE."First Name",
       CAST('MASKED' AS varchar(40)) AS "Address",
       CAST('MASKED' AS varchar(40)) AS "ZIP",
       CAST(TRANSLATE(SUBSTR("Card", 1, LENGTH(TRIM("Card")) - 4), '0123456789', 'XXXXXXXXXX') || SUBSTR("Card", LENGTH(TRIM("Card")) - 3) AS varchar(20)) AS "Card"

Related Articles