2.18.3 Masking User defined data
Apart from factory shipped seed data, additional user identified PII data can be
masked by uploading an input file with field details and processing it in Data Masking
screen using input file processing method.
- On identifying the fields, create an input file (in text file format) with table
name, column name, and enabled indicator (Y/N) for each field level record. If
enabled indicator is N, the record is not processed for
data masking.
For example, BUSINESS_APPL_DETAILS,BSD_LEGAL_NAME,N
- Place the input file to the path as defined in system parameter IPI_DIRECTORY. For example, $OFSLL_HOME/input/ipi
- Navigate to Setup > Administration > System > Batch Jobs screen and
execute the following batch job:
Table 2-87 Masking User defined data
Set Code Description Job Code SET-IFP PI INFROMATION FILE UPLOAD PROCESSING IPIPRC_BJ_100_01
On execution, the batch job picks the file from the location, processes it and loads the seed data into Data Masking screen. By default, all the user identified PII data from input file is categorized separately in Data Masking screen by assigning the value of System Defined property as N.
Once the data is available in Data Masking screen, enable the required
fields, assign user responsibility and run the processing batch job - redprc_bj_100_01
to generate a redaction policy. For more details, refer Create data redaction policy section.
Note:
In addition, an xml sample file with PII fields data is provided in the installation bundle (docs folder). The same is generated through Application Data Model (ADM) and can be imported to view the details of PII masked fields. However to do so, you need to have Oracle Cloud 13c installed.Parent topic: Data Masking