Data Security (PII - Role based restrictions)

AE RPA complies with the requirement of masking of data (Data is masked as per the masking pattern) and anonymization (one-way data encryption) of the Personal Identifiable Information (PII) data in custom business Reports.

 

This feature has been extended to Process Input defined in Automation Studio to be included as PII data in existing OOB Reports as well. PII can be defined as any personal information about any person with which the person can be identified. 

 

Mainly, the PII data includes:

• Full name
• Country, State, City, Pin code
• Credit card
• SSN and so on.

A data masking is a process which hides the confidential part of data. Data protection feature ensures that sensitive data is protected in the RPA work environment.

 

NOTE:

During process configuration and reporting of profiling data, customers should inform users before doing individual analysis and profiling. During process configuration there should not be any personally identifiable information (PII) data components in the data or content in the e-mail, messages, or system comments. By default, OOB Dashboard in Reporting will show data for all the profiles. However, you can restrict the data appearing in OOB Dashboards by mapping the particular profiles in the User Mapping section of the Administrator Module. To perform role access, and dashboard configuration, see see Specify Role Access.

 

Prerequisites

Ensure that required masking pattern/Anonymization has been applied for an argument through Data Protection in Automation Studio. For more information about masking, see Data Protection section in Automation Studio. 

• Data can be masked or anonymized for Operational reports as well as Business reports.
  
  For more information about masking pattern, see Specify Role Access.