GDPR: what’s new and what’s old
GDPR 2018: what’s new and what’s old.
In my work as a privacy professional I have dealt with companies and public administrations that – those with more effort and effort, those with less – have tried to adapt to the so-called “privacy” regulations that have taken place over the last twenty years. But when I happened to meet these companies after a while, I discovered that all those efforts – big or small they were – had no following: a magnificent castle was built but no maintenance was done , and that castle fell to pieces, in some cases it no longer exists and many do not know if it ever existed.
So when I think of the GDPR and all those who are concerned with the changes that this introduces and the investments that will need to be made to adapt, in short, when my clients ask me how much this new castle will cost them, I would rather say than think what will be needed to invest in building the castle (new software, new technologies) will be more important to think about later, how to organize and maintain their processes, how to keep their people up to date, how to verify, monitor that data are treated in the respect for the principles, that the effectiveness of the security measures is always adequate in relation to the evolution of the threats and the new treatments that the companies put in place.
Yes, because in the GDPR there is little new as to prescriptions (the GDPR has not so much prescriptive character), there is instead a lot of new in terms of principles and responsibilities.
One of the key principles of the GDPR 2018 is in fact that of accountability, of accountability.
In fact, the Owner is responsible for any decision on the appropriate measures to be prepared, and the measures are established on the basis of the results of the risk analysis (and this is not new, remember the DPSS whose compulsory had been canceled in our legal system?). And the risk analysis must be done on the treatments, it is necessary to draw up a Register of Treatments (The DPSS foresaw a census of the treatments, even here nothing new …).
But security measures, treatment processes, are not something static. Moreover it may happen that not all organization is constant in applying principles and measures in daily practice.
Here then the GDPR requires that the effectiveness of the measures is monitored, that the application of the principles is verified: this has only one name, which in the Italian version of the GDPR has been translated in an abrupt manner in three different ways. This name is AUDIT: here’s what you have to keep doing.
And much attention must also be done when designing new measures, new treatments: it will be necessary to respect the key principles of privacy by design and privacy by default.
And for the most risky treatments (those that are operated on data that are risky for the freedom and dignity of the data subjects, health data, biometric data, genetic data …), an Impact Assessment must be carried out before starting the treatment. The current legislation provides for a notification to the Guarantor, an act that is usually only bureaucratic: the GDPR asks for something more complicated, which goes to intersect with the principle of accountability: it is always the owner who is responsible for carrying out an evaluation impact and decide on the measures.
In conclusion, in GDPR 2018 there is a lot of old, already present in the current legislation, although in some cases a bit ‘hidden between the lines, but often less hidden in the measures of the Guarantor. The real news, as we have seen, lies in the responsibility, in the need – even in the obligation – to do maintenance, and it is precisely there that also go to fit the new (those yes!) And much heavier penalties.
Paolo Raimondi, Privacy Officer and Privacy Consultant
- Long-term search: what’s new in the SOCaaS service
- Plesk panel: available applications
- Acronis Active Protection: defense against ransomware
- Insider threat: identifying and fighting them
- PageSpeed Insight: better speed with Google
- ClearOS: Linux Server for Small Business
- UEBA: Behavior Analysis Explained
- Node.js via SOD hosting panel
- Backup as a Service (2)
- Cloud Conference (3)
- Cloud CRM (1)
- Cloud Server/VPS (18)
- Conferenza Cloud (2)
- ICT Monitoring (3)
- Log Management (2)
- News (16)
- ownCloud (4)
- Privacy (6)
- Secure Online Desktop (14)
- Security (5)
- Web Hosting (11)
- Microsoft Cloud Security Exec Talks New Tech, WFH, Gamification
- Kmart Hit by Egregor Ransomware
- BECs and EACs: What's the Difference?
- ProCaster LE-32F430 SmartTV RCE via libsoup/2.51.3 stack overflow (CVE-2017-2885)
- New BlackArch Linux ISOs + OVA Image released!
- Intel Doubles Down on Emerging Technologies for Sharing and Using Data Securely
- Campagna di phishing contro la supply chain del vaccino anti Covid-19 (NE01/201204/CSIRT-ITA)
- Vulnerabilità RCE su IBM Spectrum Protect Plus (AL01/201204/CSIRT-ITA)
- Flash Dies but Warning Signs Persist: A Eulogy for Tech's Terrible Security Precedent
- Assessing Cybersecurity Risk in Today's Enterprises
- Potential Nation-State Actor Targets COVID-19 Vaccine Supply Chain
- TrickBot's New Tactic Threatens Firmware
- Researchers Discover New Obfuscation-As-a-Service Platform
- Common Container Manager Is Vulnerable to Dangerous Exploit
- Bundeswehr VDPBw 50+ reported vulnerabilities
Se sei interessato ad ospitare app di Node.js sul tuo spazio web, abbiamo buone notizie! Il pannello di controllo o… https://t.co/mL6DadwZwm
If you are interested in hosting Node.js apps on your web space, we have good news! The control panel offered by SO… https://t.co/LqsIpIMaoy
SOAR (Security Orchestration, Automation and Response) technology helps coordinate, execute and automate activities… https://t.co/iPXj1btncq
La tecnologia SOAR (Security Orchestration, Automation and Response) aiuta a coordinare, eseguire e automatizzare l… https://t.co/g7DzYmLwNb
IT systems produce large quantities of log files, very useful tools for guaranteeing data security and application… https://t.co/3OwGBzeOOo