This session will be delivered jointly by Alex Yates and Pete Moore
People who hold data about EU citizens (and who like not being in prison).
Do you hold data on EU citizens? If so GDPR applies to you.
From the 25th May 2018 all orgs that hold data about EU citizens (including US companies) must implement appropriate technical and organisational measures to ensure and demonstrate that they are compliant with GDPR. Those who fail will be liable for a fine of €20M or 4% of annual global turnover – whichever is GREATER. Also, prison.
Needless to say, as a professional who works with data it is wise to ensure that you understand GDPR.
DISCLAIMER: We are not lawyers.
Let me repeat: WE ARE NOT LAWYERS.
We are not qualified to give legal advice. However, we do know a thing or two about delivering software. In this talk we will bring your attention to the main aspects of GDPR and discuss some of the consequences this has on the use of production data and Database Lifecycle Management (DLM).
We will focus on technical problems that we need to address. You can (and should) hire your own lawyers to provide legal advice.
Why I Want to Present This Session:
Like most of us – I’m not an expert in compliance legislation. I am a database DevOps/DLM consultant. I like shipping updates, not reading legal documents. However, those law things impact my work.
Because developers like testing with production or “production like” data. If they don’t have realistic data people tend to utter the words “it works on my machine”.
So I’ve been thinking about how to support people to write and test SQL code effectively while attempting to stay compliant with the new legislation. I’d like to share what I have learned, from the perspective of a DevOps consultant, rather than that of a lawyer.
As I’ve said before – I’m not a lawyer, I don’t claim to be a lawyer, don’t sue me.
GDPR is scaring more people than it ought. This is because GDPR is the opportunity to, not only get your Data estate in order, but to requisition the funds to do so. Organisations that don’t take this seriously might get left behind. Ipso facto, those that do will lead.
I want to do this session because the GDPR is fair. Fair on the data subject (and whoever you are that means you) because their rights are made relevant. Fair on the organisation that gets to realise its data potential whilst jettisoning its Data dross. And, ultimately, fair on, you, the Data Scientist because their muse is made legal.
Data bloke. Keeps it simple. Gets it done.In today’s world finding the information is easy, asking the correct questions of it: that’s hard. The single best way to ask the right questions is to look at your data. This is what I do: look at the data, ask the right questions, solve the right problems. LinkedIn, Twitter
*Header image is shared under the CC0 1.0 Public Domain Dedication licence
Latest posts by Alex Yates (see all)
- €20M+ fines and prison: General Data Protection Regulation (GDPR) is coming. What does this mean for DLM? - July 13, 2017
- Getting CI right for SQL Server - June 2, 2017
- DevOps 101 for data professionals – how your jobs will change - January 20, 2017