This year has been filled with data privacy and protection concerns. From the introduction of the General Data Protection Regulation (GDPR) and the exposure of data breaches at Cambridge Analytica, Facebook and Under Armour, to new legislation springing up in the US, including New York’s Stop Hacks and Improve Electronic Data Security Act (SHIELD) and the California Consumer Privacy Act (CCPA). Stories about the value of data – and the risks associated with it – are everywhere. As data professionals, the pressure is there to achieve a balance between compliance and the need to deliver faster than ever.
On May 25, 2018, European privacy law is going to enforce new global standards for privacy rights, security, and compliance. This new regulation is known as GDPR – General Data Protection Regulations. Lots of users who are using SQL Server often wonder How to make SQL Server GDPR compliance? Before you read this blog post, I suggest you read my earlier blog post about here which explains everything about GDPR. This blog post we will take about Authentication in SQL Server (Windows and Mixed Mode) which is for GDPR Article 25.
I am really not sure how many times I have been asked about GDPR Compliance in the recent months. You must bookmark this page and share with your organizations if you are doing business with European Union or firm based out of European Union.
It is quite often to see the email in mailbox with the following title –
How to Make SQL Server GDPR Compliance?