SQL Server 2016 - Data masking

Dynamic Data Masking(DDM)
  • SQL Server 2016 introduced dynamic data masking (DDM) as a way to prevent unauthorized users from viewing sensitive information.
  • The database engine masks the data when it is retrieved from the database, based on masking rules defined on the column schema. 
  • IMPORTANT - The data stored within the database remains unchanged.
  • When a user queries the database, the database engine determines whether that user account has the permissions necessary to access the data in its unmasked state
  • It is implemented within the database itself, the logic is centralized and always applies when the sensitive data is queried.
  • It is quite simple to configure DDM rules on sensitive column
Key points to consider;
  • DDM is not a replacement for security access control mechanisms, nor is it a method for encrypting physical data. 
  • Data masking performance impact is minimal and often negligible
  • SQL Server 2016 and Azure SQL DB are the only platforms supporting data masking
  • It can be applied on table and not on view. View will inherit the masking permissions from respective table.
References

Comments

Popular posts from this blog

Setting up Dotnetnuke (DNN) to work with Active Directory

SQL Server 2016 TDE ( Transparent Data Encryption)

jQuery Tips for DotNetNuke Developers