Data Masking

Many organizations inadvertently breach information when they routinely copy sensitive or regulated production data into non-production environments, typically as a method of giving Developers and Application Tester's meaningful data and reasonable data volumes with which to work. Databases that contain highly sensitive information may also be entrusted to vendors for development of bespoke applications. Data in non-production environments expose organizations to data theft and unauthorised access to sensitive information, as non-production environments are typically unsecured and allow unhindered access to company data. Just like data breaches in production environments, data breaches in non-production environments can cost millions of Rands to remediate and cause irreparable harm to reputation and brand.

One method of protecting information in circumstances such as these is to mask the data within the tables, thereby hiding sensitive information such as account numbers, Credit Card numbers, names and addresses etc. Developers, testers and external parties can still have a database with meaningful information and suitable volumes, but just not actual data.

MyDBA can custom develop data masking procedures that will protect an organizations sensitive information from theft or unauthorized access, once outside of the production environment, by replacing sensitive data with randomly generated numbers and text.

We offer the following data masking service:

• Customer selected tables and data columns.
• Flexible customer specific rules and masking requirements.
• Referential constraints remain intact even with masked column data.
• Randomly generated numbers and letters.
• Special character handling.
• Full exception handling and reporting.
• Restart able procedures.
• Performance tuned for large database.
• Masking process logging and reporting.

MyDBA's Articles On Data Masking

• Data Masking - What Is That And Why Do We Need It?