May 15, 2016 at 10:31 pm
Comments posted to this topic are about the item Dynamic Data Masking
May 16, 2016 at 7:07 am
It may serve us well for the HIPAA regs.
May 16, 2016 at 10:02 am
Iwas Bornready (5/16/2016)
It may serve us well for the HIPAA regs.
It'll be interesting to see what shakes out there. As stated in the article, it's not a form of encryption and does nothing to protect data at rest or protect data from someone that has certain privs, like DBO, etc.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2016 at 2:45 pm
Yes, not a great feature for true data security, but good for keeping non-priv users from seeing data they shouldn't. :ermm:
May 17, 2016 at 7:49 am
**CORRECTION**
A friend from Microsoft pointed out to me that there have been some changes to the Data Masking feature since earlier releases...
One of the 'Cons' I mentioned (Masking can be ‘unmasked’ by using a CAST statement) is an issue that has been resolved, and is no longer a limitation in the upcoming RTM version.
Also, the security enabled connection string was a requirement for Azure SQL Databases in the earlier version, but it no longer relevant.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy