11 ms·
GDPR: sorting the fact from the fiction
- woolvalley 9y ago"Trust us, we won't use this big stick that has no legal repercussions from us using it."
- Sylos 9y agoNot like they get enjoyment or an advantage by using that stick.
- b4lancesh33t 9y agoSarcasm often doesn't come across on the internet. Is my surmise that you are joking correct?
- Sylos 9y agoI was not joking or sarcastic. They are a regulatory institution. They get paid to look after companies, so that those keep to the law. Presumably, the workers at this institution do not get paid for how high the fines are that they can push through. Nor does their office get paved with gold floors. So, they have no incentive to swing the biggest stick they have. There's no concrete reason to distrust them here. Really, part of their job description for which they do get paid, is probably that they should not fine companies inadequately. If companies leave the country or even just do less business there, that's probably more damaging to the country than recieving that one-time 4% of turnover.
- AndrewKemendo 9y agoI think this ignores the reality of who populates these beuraucracies. I worked for the DoD alongside the FBI, NSA and others and the sheer delight that case agents and officers get for "hammering" people/entities under scrutiny cannot be overstated - it's part of the ethos. It has little to do with how much they get paid. It has everything to do with wielding power backed by a state enforcement entity.
- rahoulb 9y agoYet when the Cookie Law came out the ICO basically said "we know it's complicated, it's an education job, not an enforcement one".
- ggg9990 9y agoOf course “they” do, the EU collects billions of dollars in protection money every few years from each of the tech giants.
- IncRnd 9y agoTrust us. We're from the government.
- eoincathal 9y agoAs opposed to "Trust us, we're Google/Facebook/Doubleclick/etc"? Not arguing for government necessarily. Just wonder who or what else would be the honest booked?
- IncRnd 9y agoI was mirroring comments that were made in the article. > Just wonder who or what else would be the honest booked? Could you rephrase that question, please? I'm not sure what you've asked me.
- alphaalpha101 9y ago>Issuing fines has always been and will continue to be, a last resort. Last year (2016/2017) we concluded 17,300 cases. I can tell you that 16 of them resulted in fines for the organisations concerned. That's very disappointing.
- nrjames 9y agoEh... that's the voice of one regulator and you never know who may decide to be more draconian with the regulations. My suggestion is to read it yourself and think carefully about the various data protection and portability requirements. IMO, all it takes is a small band of trolls who want to harm your company to start to cause problems. Here's a clear way to read through it: https://www.privacy-regulation.eu/en/index.htm https://www.privacy-regulation.eu/en/index.htm
- bsder 9y agoOne thing I don't know is: Is this a law? Is there judicial oversight? Is there judicial approval first? If this is something that a motivated executive can apply unilaterally, it's bad. If this is something that can only be applied after a judicial system rules on compliance and gives you the opportunity to fix the issue, then it's probably okay.
- tyfon 9y agoGDPR has been in "preview mode" for two years but it is currently the law in many countries. It will start being enforced in May so you already have had two years to fix the issue if I read you correctly.
- closeparen 9y agoExtraterritoriality is new. Most websites are probably not in the business of complying with the law in random EU countries where they have no legal or logistical presence. HN, for example, doesn’t.
- cinquemb 9y agoWell, let's not pretend that it will stop EU countries from trying to engage in this glorified rent seeking exercise cum morality play against companies everywhere.
- 9y ago
- brad0 9y agoThe tone of this article feels very different to the words she’s saying.
- eadmund 9y agoThe thing which bothers me the most isn't the fine structure — steep fines for bad behaviour are fine (pun intended) — it's the so-called 'right to be forgotten.' It essentially makes simple immutable logs illegal. I'm still not certain how we're going to handle it. Encrypting each record with a per-identifier key works, but that makes doing anything with the data as a whole prohibitively expensive. And there's the whole question of what counts as identifying information. My understanding is that IP addresses do — so an immutable plaintext server log is now illegal. Privacy is really, really important. But expanding the definition of privacy too far is just too much.
- snowball2 9y agoBackups also...
- mappu 9y agoIt's not clear how to implement 'right to be forgotten' inside backed-up data, too.
- geocar 9y agoIt’s pretty easy: just don’t restore their data. Most businesses with personal data also have invoices. Since you don’t have to destroy those, simply note their request there. Other kinds of personal data like marketing leads and medical data should be much easier to see how to forget.
- hamandcheese 9y agoThat isn’t easy from a technical perspective. The whole point of a backup is to restore to a state from a previous point in time... now they want future state (the “right to be forgotten” request) to modify how a backup should be restored?
- geocar 9y agoNo. The whole point of backups is to protect against hardware failures and unforeseen software bugs/defects. If someone sends you something in the post telling you to delete their data, it should not be difficult to simply keep that record available when you need to restore an unrelated machines backup, unless you have incompetent IT. This is part of the reason many GDPR consultants suggest applying an IT standard like ISO so that it’s clear you already know what backups are for and how to use it. A single machine/database with all your business data on it mixed with personal data and the only record of requests from subjects is criminally irresponsible.
- microcolonel 9y ago> Focusing on big fines makes for great headlines, but thinking that GDPR is about crippling financial punishment misses the point. And that concerns me. Translation: the fact that the fine structure and breadth of covered activities is considered rather extreme, even by the general public, is not part of our desired narrative. We aren't saying that some businesses can't be totally destroyed by just one of these fines, we're just "concerned" that people see that as somewhat pivotal. And who on Earth is she to think that her concern is a rebuttal? The Commissioner can be concerned about anything she likes, it doesn't justify any particular action.
- fencepost 9y agoI haven't really dug into it being in the USA, but from what I've heard the big takeaway for my clients might be: "You can never again accept a European as a patient, and for your own protection you might need to dismiss any European patients you have." I'm not really worried about legitimate cases where someone wants their data removed, as that seems unlikely. I'm less sure about the risks of some enterprising young lawyer over there finding a way (or a possible way that would end up thrown out) to leverage it to extort money. Read at its bluntest, as I understand it this law seems to basically ban backups, at least those retained for any significant amount of time. Have a customer/patient database on a cycle of daily/weekly/monthly backups that get pruned as they get older? You need to be able to purge any individual who requests it from those backups. Have regulatory or contractual requirements on keeping records? Well, that's what the courts are for, hope you like the attorneys you're going to be paying. Heck, for medical practices I've heard of insurance companies doing clawbacks of payments years after the date of service - what does a practice do if it serves a European with temporary insurance, gets a request to purge that person's data, then gets a request for clarification from an insurance company? Perhaps this is a complete non-issue for US companies, but I'm not so certain of that that I'd be willing to just dismiss it out of hand and if it's not dismissed then parts of it are pretty scary.
- geocar 9y agoI’m currently doing GDPR consulting for an American company. The GDPR doesn’t ban backups. You must inform the subject of how long you keep those backups though. If payment processing stays open for years, then years is fine. I have a customer who keeps data for ten years. The GDPR doesn’t say that a European can claim “right to be forgotten” and force you to destroy invoices proving you did Work for hire. If for some reason they want you to stop processing (right to object) then they end up owing the money themselves- since they can’t force you to forget the invoice, having you unable to send their invoice to insurance sounds like a bad move on their part. Reading the GDPR “at its bluntest” is not the correct way to do things: European courts are not amused by a narrow view of the law when it is used to argue something is technically legal, not do they use their maximum force for minor infraction. That’s why you don’t need to worry about an “enterprising” European taking you to the cleaners because the courts won’t think it’s funny either. It also means that if you know what personal data you have, what you do with it, disclose to the subject those things including who specifically you share it with, and protect that personal data like your business depends on it, then you’ll be fine because the point of the GDPR is that this is what you should be doing.
- Azeralthefallen 9y agoHonestly i think the GDPR is a great idea, unfortunately after going through 3 different firms who are supposed experts on the GDPR. We are still struggling. When you ask them about a possible situation, and the response you get is "that is kind of a gray area", to "that is open to interpretation". For example nobody has been able to give me a clear definition of what counts as identifying information. I have heard IP addresses count, so what about our cloudfront logs? They have the client ip address. If i pipe them straight to a logging SaaS, is it on the logging service to handle it? Or is it on me? Furthermore for the right to be forgotten, how do i handle that with backups that are not under our control? E.g. AWS RDS backups? Amazon says there is no way to modify those backups, and our TAM has suggested managing our backups our selves. What about data that our customers pipe to our service, how is that handled by the GDPR, it is all encrypted. But apparently we need to handle cases, but we don't have the decryption keys. Is it on the customer who uses our SaaS or is it on us? How do these scenarios work? While i feel more and more we are ready for the GDPR at the same time i am terrified. I feel many of the laws can be interpreted far too many different ways which makes me uncomfortable.
- geocar 9y agoAllowing the court to decide makes it possible to interpret degrees of wrongness and malice of intent. IP addresses may be personal data if you have a database containing personal data (like a web form) and the IP address. Don’t have that database, or only make it accessible to your firm and processors to verify data integrity/protect against fraud: no problem. Dropping the IP column from that table after a month is probably easy enough and good enough. The GDPR also doesn’t mandate encryption. It says you’re responsible if you get hacked and could’ve prevented it. Applying an IT security standard (eg ISO) is just one (probably easily) defensible way to do it. Not getting hacked is another. Your consultants should fully understand your business and data flows: individual things taken in isolation are a “grey area” but looked through the lens of your whole company, actions and intent, versus value to the subject themselves (instead of just your customers) is what the European courts will do if they decide to give your company attention; they will not nit.
- jcranmer 9y agoThe GDPR strikes me as an urexample of regulations gone wrong. If you read some of the later posts in this series, one thing they say is that "the regulation can't be that onerous because this is all best practices anyways." But the reason the regulations are onerous are because what qualifies as falling under the purview is indefinite, and the regulators don't want to clarify so they can use the ambiguities to punch the punching bags when the opportunity arises. So the risk-averse have to assume that the requirements stretch to the truly insane (e.g., requiring an email for anti-spam blog commenting purposes triggering these provisions) with the only guidance really being "we're not really targeting you; we just care about the punching bags."
- cobookman 9y agoGoogle cloud has a good blog post summarizing gdpr https://www.google.com/cloud/security/gdpr/ https://www.google.com/cloud/security/gdpr/
- tyler_larson 9y agoThe GDPR was specifically sold as limiting the things that well-known US tech companies (Facebook, Google, Twitter, etc.) can do with respect to EU citizens. The sad irony is that only well-resourced tech companies with a small army of lawyers and a large army of programmers can afford to be GDPR compliant. The sort of unintuitive machinations it takes to maintain honest compliance while providing useful services is kind of mind-blowing. Every bit of it that I've delt with has left me depressed about what this will do to small companies and innovation. Facebook will have no trouble at all being GDPR compliant, but your average 50-person startup or small-town business hasn't got a chance.
- Joeri 9y agoThis is exactly the sort of scaremongering this article was trying to address. Being compliant is about not abusing personal data. I think small companies will find that much easier to do than bigcorps whose business model is based on privacy invasion, like facebook or google.
- geocar 9y agoI’m currently doing some GDPR consulting for an American company. I don’t think the GDPR is as difficult as you suggest. The biggest problem companies seem to struggle with is this idea that the personal data they keep isn’t theirs and they need to protect it like anything else in their possession that isn’t theirs. Then, there’s also the issue that Americans aren’t used to the idea that a European court might think they’re in their jurisdiction, and they don’t know how to interact with a European court. Treating them as adversaries (as is often done in the USA) doesn’t go well. The courts basically decide if you fucked up and did harm that you could’ve prevented, and not if you were technically against the law. Are you treating someone’s personal data the way they would want you to? Really? If so then you’re probably better than 90% of the way there.
- Silhouette 9y agoI don’t think the GDPR is as difficult as you suggest. The biggest problem companies seem to struggle with is this idea that the personal data they keep isn’t theirs and they need to protect it like anything else in their possession that isn’t theirs. You keep writing things like this, and I'm not going to just post the same reply every time, so let's try another one here. Let us assume for the sake of debate that Privacy Shield will at some point be struck down by the courts, like Safe Harbor before it, since the fundamental objections involving US government access have not changed. At that point, please explain the conditions under which an EU business can share PII with a US business without violating the GDPR.
- rdtsc 9y agoWonder how much of a secondary consultancy market this is going to create. I can just see "GDPR consultant charging $450/hour with a minimum 2 weeks worth of work" job listings. It would be interesting what companies do about it. Will any of them pull out of the EU market. Or maybe make users sign away their rights on their next login "If you use this service, you give us permission to use your data in this and that way which may or may not be GDPR compliant, if you refuse we'll delete your profile and you'll have to find an another service to solve your problem". As a consumer, I like what GDPR is doing. As a developer having to implement compliance for it, it is a huge pain.
- matthewheath 9y ago> Or maybe make users sign away their rights on their next login The GDPR explicitly disallows this. You're not allowed to make access to your service conditional on consent because it's considered to be "not true consent".
- wtfstatists 9y agoExpanding on this, official guideline on consent [1] gives 2 relevant examples. TLDR: you cannot offer no, degraded or higher-priced service if consent is not given. I would say this is effectively banning targeted ads as revenue stream. IMO this goes too far. [Example 1] A mobile app for photo editing asks its users to have their GPS localisation activated for the use of its services. The app also tells its users it will use the collected data for behavioural advertising purposes. Neither geo-localisation or online behavioural advertising are necessary for the provision of the photo editing service and go beyond the delivery of the core service provided. Since users cannot use the app without consenting to these purposes, the consent cannot be considered as being freely given. [Example 6] A bank asks customers for consent to use their payment details for marketing purposes. This processing activity is not necessary for the performance of the contract with the customer and the delivery of ordinary bank account services. If the customer’s refusal to consent to this processing purpose would lead to the denial of banking services, closure of the bank account, or an increase of the fee, consent cannot be freely given or revoked. [1] http://ec.europa.eu/newsroom/just/document.cfm?doc_id=48849 http://ec.europa.eu/newsroom/just/document.cfm?doc_id=48849
- gressquel 9y agoOur company receives sensitive data from external members by email, which is considered insecure. So we need to buy or create our own solution to receive these files encrypted. Does anyone here have github repo to such a solution?
- kuschku 9y agoYou could use the system the big US banks use for that: FTPS or SFTP. Alternatively, you could simply set up a cloud share they can upload files to, e.g. a Seafile instance, and have them link it in the email. If you want to go fancy, you can build your own HTTPS protected upload form. Or you can use OpenPGP / GPG / PGP for your emails. This isn’t exactly rocket science.
- JdeBP 9y agoWhilst the point about this stuff being well known is sound, I shall just point out that FTPS alone is quite likely (according to circumstances of course) to be not enough. I know of at least one system that already used FTPS for a decade or so that now has to be modified to use GPG encryption as well, for GDPR compliance. Security of data once they have arrived is as important as security of data that are in transit.
- tombrossman 9y agoScott Helme has a self-hosted contact form which uses his PGP key to encrypt messages from website visitors, with a link to his 'how to' blog post just below the form: https://scotthelme.co.uk/contact/ https://scotthelme.co.uk/contact/
- darkport 9y agoYou're e-mails are probably using TLS (I would check), which is the same as HTTPS. SFTP would be ideal.