Applying Masking from Scheduled Discovery Results

the add masking action allows masking to be applied directly on scheduled discovery results when a masking method is saved, it is enforced immediately on the target database and also persisted under the selected policy group as an autogen policy entry no manual rule creation is required in policy management to apply masking in sensitive data discovery 1 navigate to sensitive data discovery and open the schedule result page 2 click options > show details to view column level matches 3 select the row for the column to be masked confirm table, column, and match % 4 click actions > add masking to open the dialog 5 in policy group, select a group appropriate for the target device (for example, oracle pg) 6 in masking method, select a method compatible with the column’s data type (for example, oracle first name) 7 click save masking is applied immediately and an autogen rule is created under the chosen policy group verifying masked data after saving, verify the masking in a database client open a sql client (for example, dbeaver ) and re query the same table confirm that in scope fields return masked values (for example, john →“ n” , emma →“ a ” ) managing the generated policy the system writes the selection as an autogen entry in the selected policy group navigate to policy management > groups > {selected group} confirm an autogen rule exists and is active to revert, disable or delete the autogen rule and re query the table to confirm original values are returned · only masking methods compatible with the column’s data type should be selected · if no suitable policy group exists for the device type, the policy group list will be empty · the add masking action is available only for completed scheduled jobs