DataSunrise Masking for GaussDB

DataSunrise masking for GaussDB obfuscates real sensitive corporate data making it unreadable for non-privileged users. With the masking possibility, you can hide data whenever and wherever you want. Unauthorized users can not view the real data, so you can easily provide information and prevent data leakage.

DataSunrise allows you to protect sensitive data stored in GaussDB from leakage. Thanks to replacing real data with fake ones you will be able to share your data with third parties, such as testers, developers, sales teams, or other unauthorized users who do not need to view real data to do their job. Moreover, DataSunrise preserves the format of the real data so there is no need for changes in application architecture. DataSunrise supports both dynamic and static data masking. They are based on the same algorithm but have differences in the way they are used and applied.

Static Data Masking creates a copy of the source database and changes sensitive data in the copy. It means that the real data remains the same and does not undergo any changes. When you use Static Masking there is no possibility to retrieve real data from the masked values. But you should remember to update the copy of the database as soon as you have new sensitive data.

Dynamic Masking does not create a copy of the database because the masking is made at the moment of the query. In this case, data does not leave the database. DataSunrise intercepts the query and changes it according to pre-set masking rules. After that, the user will have the masked data.

With Data Masking from DataSunrise for GaussDB, you will be sure that sensitive data will not be revealed to a third party. Data masking helps you to stay in compliance with different data protection regulations and protect sensitive data from unauthorized access.