Fonctionnalités de Data Masker for Oracle

Why sanitize data in test databases?
Sanitize
Remove the risk of inappropriate data visibility.
Mask
Adopt a simple, repeatable process.
Repeatable
Customize data masking rules at scale
Customize
Why sanitize data in test databases?

Why sanitize data in test databases?

For legal and practical business reasons. A leak of sensitive information (particularly consumer data) from a test database can cause a devastating loss of public confidence, and the possibility of legal liabilities.

Remove the risk of inappropriate data visibility.

Remove the risk of inappropriate data visibility.

Data Masker is an inexpensive way to eliminate a large security problem. The test data looks real - your development teams will never know the difference - and yet the sensitive information content remains completely secure.

Adopt a simple, repeatable process.

Adopt a simple, repeatable process.

Securing sensitive information with Data Masker is a simple, repeatable, push-button process which can be quickly applied whenever a test database is refreshed with production data. The consistent update of denormalized data after masking is simple. Data Masker contains custom synchronization rules for all three challenges: Synchronizing data at the row level, ensuring consistency of newly masked data between rows in a table, and maintaining the consistency of data between tables. Configured masking rules can be saved and re-run at any time.

Customize data masking rules at scale

Customize data masking rules at scale

A broad range of replacement datasets are included with the Data Masker software and it is possible to add your own user defined collections of data for specific cases. Each edition of Data Masker (Oracle and SQL Server) is specifically written for the target database architecture. Data Masker is fast, and is designed for extremely large and complex systems.