The General Data Protection Regulation (GDPR) is a set of rules to improve the protection of data about European citizens. Quote from this link:
The EU General Data Protection Regulation (GDPR) is the most important change in data privacy regulation in 20 years.
Refer to GDPR Key Changes for a summary of what it is all about, especially the Data Subject Rights, such as:
- Breach Notification.
- Right to Access.
- Right to be Forgotten.
- Data Portability.
- Privacy by Design.
Some GDPR facts:
- GDPR will be enforced as of 25 May 2018 (that's pretty close).
Quote from GDPR Key Changes (about Territorial Scope):
... will apply to the processing of personal data by controllers and processors in the EU, regardless of whether the processing takes place in the EU or not. The GDPR will also apply to the processing of personal data of data subjects in the EU by a controller or processor not established in the EU, where the activities relate to: offering goods or services to EU citizens (irrespective of whether payment is required) and the monitoring of behaviour that takes place within the EU. Non-Eu businesses processing the data of EU citizens will also have to appoint a representative in the EU.
For anybody who is old enough to remember the Y2K-hype back in the 90s (i.e. the impact of it on IT systems): IMHO addressing all those Y2K issues was a piece of cake as compared to the challenge ahead with this GDPR thing.
Question(s): What is the impact of GDPR on DevOps, more specifically I wonder about:
- What kind of changes will be needed in the DevOps toolchain to make them GDPR-compliant?
- How can DevOps-practises help (facilitate, simplify, etc) a company to become GDPR-compliant, similar to how SCM tools helped in the 90s to become Y2K compliant?