Oracle Data Masking & Subsetting Pack (Building Up-Sell/Cross-Sell Opportunity)
Recently I come across with one query from partner that whether Oracle Data Integrator can mask the data or not. I knew Oracle has solution for masking data which provide flexibility, reduce time and save from management hassles there are techniques available. I wanted to know its true capability from integration standpoint. However, further digging, I find its unique features. So, decided to share my understanding with all of you to see it as upsell/cross sell opportunity. As this is one of the concern of all the organization to secure their sensitive information within data while sharing with internal as well as external teams.
Data Masking market is expected to reach $435 million by 2025 at CAGR of 15.03%. With the increase of data analytics (details can be obtained from the link given below in the references), there is substantial rise in the concern of data security and privacy throughout the world. This will surely accelerate the need of data masking in coming days. In fact, many of our customer’s conversation, we have seen this concern of sharing data with the downstream applications or within the teams and we getting queries regarding data masking tools.
Many of you must be knowing that “Oracle Data Masking & Subsetting” is a solution pack for Oracle Enterprise Manager, which helps you to manage data securely. Most common use case of Oracle Data Masking & Subsetting is to offload sensitive data into non-production or development environment along with ensuring security. It has two basic functions i.e. Masking data of any column specified in the table of specific schema, and Subsetting (extracting required data from tables for sampling, development or testing purpose).
Although this is usually good for migrating, data between different environments i.e. test or development etc., however it can also be used to mask the data for downstream application where sensitive data should not be visible or required.
There is another feature called Application Data Modelling that helps to automate the discovery of column with sensitive data and also corresponding referential data i.e. Foreign Key relationship in the database. This process uses inbuilt extensible patterns.
For masking data, there are various out of the box masking formats available in the pack. These includes shuffle, blurring, encryption, randomization, compounded, Conditional or custom build using defined PL/SQL formats. It is also possible to mask numbers, Strings and Dates.
Not only that, it can mask data from various other databases, as well that makes is more suitable in heterogeneous environment.
Oracle Data Masking and Subsetting also supports data masking of data from any non-Oracle database, such as IBM DB2, Microsoft SQL Server, and Sybase.
You can use it as In-database mode directly masks and subsets the data within a non-production database with minimal or no impact on production environments, And In-Export mode, to masks and subsets the data in near real-time while extracting the data from a database and write to the data pump export files.
Another feature of the pack is Data Subsetting, this helps deleting unwanted columns before sharing with internal teams or downstream applications. Subsetting are of two type: Goal Based and Condition Based.
Goal based subsetting is where we want to reduce based on goals, for example, extracting 1% subset of a table containing millions of rows.
Condition based subsetting i.e. using where clause SQL. For example, extract all data prior to specific time.
Another important feature of integration of masking feature with other products. Oracle Data Masking and Subsetting is integrated with Oracle data management and testing tools, the integration with Oracle Database Life Cycle Management Pack facilitates masking and database cloning in a single workflow. Additionaly, if data is residing in flat files, xml files or any RDBMS, Oracle Data Integrator can extract these data and mask them by calling data masking in one single unified workflow.
As far as licensing, is concerned, all database servers where masked data or data subsets originates must be licensed, that means source system core count is required. Database servers to which masked data or data subsets are copied do not require a license.
That’s all for now. I am adding few references and video link below, if you want to explore it in detail.
Links:
https://docs.oracle.com/database/121/DMKSB/intro.htm#DMKSB-GUID-DA9FC359-A411-4DCA-9E01-4756358701EA
https://www.oracle.com/us/products/database/data-masking-best-practices-161213.pdf
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/dmksb/index.html
Videos:
Analytics Cloud Big Data Practice Lead - ASEAN & SAGE at Oracle | PhD Student | Founder of Mathematics community | Member of BOS UniKL
3 年Good ?ne Kavi