Anonymization for Personnal Sample Data

GEDIS Studio is able to implement efficiently and in the simpliest way various data masking technics. You will find hereafter some demos showing you how to use those technics in a concrete situation where we need to anonymize the personnal data of a Customer Relationship Management (CRM) application.

Data encryption

Data encryption allows you to easily anonymize data while being able to retreive original data if your encryption algorithm is reversible. The weak point of data encryption is that anonymized data really differ from original one. If you are to anonymize data for creating test databases, your testers certainly do not want to see binary values instead of names !

GEDIS Studio encryption rules are well adapted to data encryption for anonymization purpose. See the demo.

Data substitution

Masking data with substitution values is probably the most spreaded way of anonymizing production data for test purpose. It can also be the worst in term of the quality of the anonymized data if you do not pay special attention to produce realistic data. GEDIS Studio is dedicated to this purpose and the above demos will convince you that you should definetly use it to produce substitution values. See the demo.

Data injection

GEDIS Studio does not perform anonymization directly on databases. This allows users to split the anonymization problem into two parts: realistic data generation and data injection.

To inject the produced data, GEDIS Studio fully configurable output format lets you produce data files that fit into any import interface. You can also directly produce SQL scripts. See the demo.

Reversibility

Anonymization reversibility is crucial if you want to be able to retreive the original data from the masked data. GEDIS Studio encoding/decoding mechanism is perfectly suited for data de-anonymization. See the demo.