HOW DELPHIX HELPS ANSWER COMPLIANCE REGELATORY [Part-I]

I've meet with many customers and every time I asked this question "where are you regarding the GDPR regulation".

The answers where surprising me as the majority of theme didn't comply yet, may be because of misunderstanding, budgets, didn't find/look for right solutions.

For those. The answer is, you have to protect the personal data you own from leaving out your walls and "Noemo censeture ignorare legem".

The objective of this article isn't to explain you the GDPR I’m not a lawyer yet :), but aims to give you an overview of how delphix can help not only accelerate your compliance but also your business.

So let's have some fun with delphix masking module.

To start create an application on the masking UI

Add an environment to your application (click on save and view)

Now let's add a connector to the database we need to profile/mask

N.B : I'm using my source database, but you can also use a vdb to create the connector.

Once done, click on "Rule set" tab to define tables subject to masking

If you check what happens on your database, you will notice that the engine sends out the following orders to get the list of tables under your schema

Select distinct table_name from all_tables where owner ='DELPHIXDB' order by table_name asc;

Wait until the rule set get refreshed

Under "Inventory" tab you will see the list and structure of table(s) you checked for masking.

At the database level the engine sends orders like those to profile the table(s) structure

select TABLE_NAME as NESTED_TABLE_NAME, PARENT_TABLE_NAME, PARENT_TABLE_COLUMN from USER_NESTED_TABLES WHERE TABLE_TYPE_OWNER = 'DELPHIXDB' and PARENT_TABLE_NAME = 'EMPLOYEES';

select null as table_cat,        owner as table_schem,        table_name,        0 as NON_UNIQUE,        null as index_qualifier,        null as index_name, 0 as type,          0 as ordinal_position, null as column_name,        null as asc_or_desc,        num_rows as cardinality,        blocks as pages,          null as filter_condition
from all_tables where table_name = 'EMPLOYEES'   
and owner = 'DELPHIXDB' union select null as table_cat,        i.owner as table_schem,          i.table_name,        decode (i.uniqueness, 'UNIQUE', 0, 1),        null as index_qualifier,        i.index_name,        1 as type,        c.column_position as ordinal_position,          c.column_name,        null as asc_or_desc,        i.distinct_keys as cardinality,        i.leaf_blocks as pages,        null as filter_condition from all_indexes i, all_ind_columns c where i.table_name = 'EMPLOYEES'   and i.owner = 'DELPHIXDB'   and i.index_name = c.index_name   and i.table_owner = c.table_owner       and i.table_name = c.t;

Delphix can help you profile tables to identify and suggest masking algorithms on sensitive columns

To do so back to the "Overview" tab and create a profile job (I'm using HIPAA standard sets)

Lets profile our Employees table

Wait until the job is finished and go back to the "Inventory" tab to identify the sensitive columns and masking algorithms that where purposed by delphix to mask theme

For infromation delphix uses column names or sampling algorithm to identify the sensitive columns to be masked. You can read more about that here on the documentation https://docs.delphix.com/docs/delphix-masking/masking-engine-admin-guide/managing-profiler-settings/practical-profiling-example

To end up this post I'm going to create a masking job, wich will be used to provision masked VDBs to the non-production environment