Objective:
The objective of this blog is to provide a detailed information
about the configuration of Data Masking with an example. And also to describe
why we should opt for data masking on the database.
What is Data masking:
Oracle Data Masking enables entire copies or subsets of
application data to be extracted from the database, obfuscated, and shared with
partners inside and outside of the business. The integrity of the database is
preserved assuring the continuity of the applications.
Why there is a requirement of Data Masking:
As we all aware that data is the at most precious and valuable
thing for any organization. And it cannot be shared or misused at any single
point of time. The data for the sensitive columns present inside the database
cannot be present with actual values on to the development, test environment or
even to the OEM (sometimes it may happen to share the data with the OEM for any kind of issue resolution of
customization etc.). If the data needs to be shared within or outside the
organization then the values present in the sensitive columns must be changed
so as to ensure data security.
Important Points must be taken into careful before
applying the Data Masking:
a) Data Masking is a separate license product available with
Oracle Enterprise Edition (Extra Cost). This requires "Oracle Data Masking
and Subsetting Pack" license for configuring and applying to the data
sets.
b) Data Masking is a very vital thing and once it is applied to
the data cannot be reverted back. So this must be double checked that data
masking configuration is not getting applied to the production database. This
need to be applied to the destination database, like development/ test
environment and when data is transported outside of the organization.
Data masking flow presentation:
This example has been tested with Oracle Enterprise
Manager 13c R4 and Oracle Database 12.1.0.2.
The detailed step-by-step configuration and test as follows.
1. Login to
Enterprise manager 13c R4.
Click on
Enterprise è
And select
Quality Management à Application Database Modeling
2. This Scree
will appear for creating a new Application data Modeling.
3. Click on
create à
Update the details on (Create Application Data Model Page)
4. Click on Continue à Select the appropriate schema. à Continue à Submit.
Now wait for the status to be change to complete. (Most recent job status will update with Succeeded.)
5. Now select
the appropriate ADM created and click on à Edit.
6. This screen
will appear.
7. Select the
“Sensitive Columns” tab.
8. Click on Add.
Update the details àSelect the column name of the object à Click on Ok.
9. This screen
will appear.
10. Now Select
the Column list and à Click on Create Discovery Job.
11. Select the
Application à
Select column type as per your requirement. à Click on Continue.
This screen will appear click on Submit.
12. Next screen job running screen will appear, wait for job to get complete.
13. Once the Job execution gets complete click on Discovery Result.
Next screen
will appear with status as succeeded.
Click on Ok
à
Click on Save and Return.
This stage
the ADM creation complete.
14. Next stage is to get ready our system for Data Masking.
Click on
Enterprise à
Quality Management à Data Masking Definitions.
15. This screen
will appear where you have create the Data Masking Definitions.
16. Click on
Create à and
Update the relative fields. à Click on Add.
17. Next Screen
will appear. Update the Schema Name and click on search.
18. Select the column name à Click on Define Format and Add.
19. Screen will
appear
20. Select the
Format entry (Like Random Decimal Number) à Click on Add. à Update the details à Click on OK.
21. Next screen
will appear click on Ok.
22. Select the
Masking definition created à Click on generate script.
23. Update the
user details and click on submit.
24. Wait for
Job to get complete.
Once the Job is succeeded à Select the Masking Definition created à click on Schedule Job.
25. Now Time to export the data with the
database object with mask value in export dump.
Update the Details and click on Submit.
26. When the Job Schedule will execute, at that time with export dump these are the file list that will get created in Dump Directory location.
Example.
28. Now Let’s Compare the Data.
The object that is not masked and imported.
29. Now the Object that is masked and imported to SH2 schema. (Column Masked are UNIT_COST & UNIT_PRICE)
Conclusion:
With this article we came to know about the importance of Data
Masking for an Organization. Data cannot be compromised or shared within in the
organization or outside the organization. For securing data in the database and
inter schema data viewing we are configuring TDE (Data Redaction and
Encryption) so that the data cannot be misused by the unauthorized users to the
database and the database system. And when it comes to the situation of sharing
the data outside the production database and to the outside of the
organization, then "Data Masking" will help in securing the valuable
data of the organization.
Twitter : https://twitter.com/TapasKarmakar
Linkedin : https://www.linkedin.com/TapasKarmakar
Blog : https://tapaskarmakardba.blogspot.com/
Youtube : https://www.youtube.com/TapasKarmakar
-------------"Keep your data safe so that you can stay safe: – Data security is must."-----------
