Commvault software has industry-standard data-masking strategies for Oracle database table columns. Use data masking when you want to hide sensitive data in a non-production environment, such as a test or development system.
To use data masking, create data-masking policies for Oracle instances that contain the following information:
The database schema
The table columns to mask
The data masking type to use for the table column. The data masking types that are available depend on the column data type. For example, if the data type is "Date", then you can use the shuffling masking type.
The Commvault software automatically applies the data-masking policies when you perform the following operations:
Clone a database
Duplicate a database
Perform an out-of-place restore, for example to a new destination client
Manually run a data masking job on the database
The Commvault software provides different data-masking strategies based on the type of data that you want to mask.
Available Masking Types
Date, Raw, Timestamp
Decimal type column
Data Masking Types
Shuffling applies to all data types. Shuffling takes values from multiple rows in a block (up to 2000 rows) and exchanges the values for the same field by using the Fisher-Yates algorithm.You can use this method for all data types, but we recommend that you do not use it for primary key or foreign key fields because it affects the table relationships.
If you use format-preserving encryption, then the masked output is the same length and format as the input, for example the masked output of a 20-character user name is a 20 character field.
Fixed string applies to character strings and replaces the original string with a random string that you specify when you configure a policy.
Numeric range generates a random number between a minimum and maximum value that you specify when you configure a policy. We recommend that you do not use it for primary key or foreign key fields because it affects the table relationships.
Numeric variance takes the initial value and varies it by the percent that you specify when you configure a policy. We recommend that you do not use it for primary key or foreign key fields because it affects the table relationships.