Dynamic Data Masker

>

• Masking preview: Rules will be created on the HTML pages in the configuration engine. To ensure that these rules have been configured correctly on the page, preview mechanism can be used.
• Role-based rule configuration engine: The configuration engine allows rules to be created based upon roles in the application (eg. Admin, Service, Tester).
• Tamper proofing of rules: Each rule file comes with an embedded hash which is re-calculated by masking engine. Any change in the rule file will lead to mismatch between the hash content. This ensures tamper proofing of rules.
• Location value-based masking: HTML elements can be masked based upon their locations.
• Screen-based masking: Along with role-based masking, screen-based masking can be used to ensure that specific sensitive fields get masked only on particular pages.
• Evidence generation: Provision of exhaustive report and ability to capture the masked preview account for evidence generation.

• High utility: Data is masked as per privacy “need-to-know” and serves the purpose without affecting utility, including allowance for exceptional work-flows
• Data Integrity: The masked data is meant only for screen presentation and does not get written into any database
• Flexible deployment: The separation of policy & execution allows for addition of any number of roles & corresponding user base
• Guaranteed fraud mitigation: The solution primarily addresses data privacy concerns
• Reduced OpEx: Companies can reduce cost in managing outsourced service providers
• High auditability: Fine-grained logging that provides accountability and evidence needed for tracing purposes