All 7 Dynamic Data Masking questions
More in Dynamic Data Masking
What built-in masking functions are available in SQL Server for dynamic data masking? How do you grant a specific user or role permission to see the real, unmasked data despite dynamic data masking being applied? Does dynamic data masking prevent a determined user from working around it to see the real underlying values? How do you remove dynamic data masking from a column once it is no longer needed? How would you apply dynamic data masking to an existing table with sensitive columns as part of a broader compliance initiative, such as meeting data privacy regulations? How does dynamic data masking behave differently when a masked column is used in a JOIN, WHERE clause, or exported through an application, compared to a simple SELECT query?
Advertisement
Back to results for “Security”
SQL Server › Dynamic Data Masking

What is dynamic data masking in SQL Server, and what problem does it solve?

Beginner

Answer

Dynamic data masking automatically hides sensitive information, like a full credit card number or an email address, from users who query a table but do not have special permission to see the unmasked value, without actually changing the real data stored in the database, protecting sensitive information from being casually viewed by everyone with query access.
ALTER TABLE Customers
ALTER COLUMN Email ADD MASKED WITH (FUNCTION = 'email()');
Real-world example A customer support team can look up customer records to help with orders, but sees a masked version of each customer's email address instead of the real value, protecting customer privacy while still letting them do their job.

Common follow-ups: Does dynamic data masking actually encrypt the underlying data?;Who is able to see the real, unmasked values?

SQL Server Security & Permissions;Transparent Data Encryption
All 7 Dynamic Data Masking questions