55 E. Monroe St.
Chicago, Il. 60603, USA
Who requires dynamic masking of data and why?
Dynamic masking of data should be used by any organization sharing data that contains sensitive information with users or systems that are not authorized to see such information. This can be due to corporate policy or privacy regulations, such as GDPR or HIPAA. Typically this includes:
Don’t miss this blog on why you need Dynamic authorization and dynamic data masking.
Organizations that utilize a proven data masking tool from Axiomatics, can ensure data is effectively shared with users across an organization, without worrying about unauthorized personnel or systems being able to see or interpret masked data. A common example of this being credit card numbers that are often logged with a provider but masked from view.
Actual credit card data
Credit card number: 7253 4111 6345 8787
User name: Jenny Jones
Masked credit card data
Credit card number: 7253 XXXX XXXX XXXX
User name: Jenny XXXXX
In this example you can clearly see how the sensitive data – in the form of the last 12 digits of the person’s credit card number along wtih the surname – have been masked, making it impossible to decipher and therefore safe to share. Without the masking technolgy this would not be possible. With fine-grained access control, data across multiple databases at table, row and cell level can be masked.
Benefits of Dynamic Data Masking
Dynamically masking data offers a number of benefits to enterprises that want to keep data intact in databases, i.e. not use static masking, but still share it securely with users and systems.
Dynamic Data Masking vs. Static Data
Static data masking involves masking data in the actual database, i.e. when data is at rest. Dynamic data masking on the other hand applies a masked layer to sensitive data when data is in transit, ensuring data in the database remains unchanged at the source. But when should you go static and when should you go dynamic?