Security

Data Privacy versus Security versus the Elephant in the Room

As always, I read with great interest David Horrigan’s look at finding a balance between privacy and crime prevention when it comes to Automated License Plate Recognition.

I think David’s take-away quote from attorney Gail Gottehrer at the end is a great effort at finding a middle-road between “track everything in case there’s a crime”, and “never track anyone”:

“Ways to maximize the benefits of ALPR technologies and minimize the privacy risks associated with them include limiting the types of entities that can collect and use ALPR data and the purposes for which they can use the data—as well as delineating when (or if) the data can be shared, and the period of time for which the data can be kept, after which it (and all copies and backups) must be destroyed,” Gottehrer added.

That sounds all well and reasonable, but it ignores one very big elephant. You can design all the rules about who can access that much data, and when it can be used, and limitations on the sharing of it, but you also have to acknowledge that, at some point, there WILL be a data breach. Whether that is by a legitimate user sharing the information incorrectly, or an outside party hacking in and stealing it, it’s likely to happen. If we’ve learned anything from the last few years, it should be that. And, we should be including that in our discussions about where we want to fall on this continuum of security versus privacy across all of society.

The balance isn’t just between being able to fight criminal activity and securing the privacy of citizens, it also has to include the reality that the data, once collected, cannot be assumed to be completely secure, and any calculations we make about which side we fall on in the debate, has to account for that. Otherwise we are just fooling ourselves.

In this case, it’s not just the risk that law enforcement will have a record of the comings and goings of any random, innocent, citizen. It’s the risk that that collection of data, if breached, could give anyone that level of detail about individuals.

Does that change the equation for you?

Similar Posts

  • |

    Not Billable Hour, Not Per-Gig, Then What?

    I’ve seen some news, and cheering, recently suggesting that per-gig pricing as part of the ediscovery process is dead. If you read that post from AccessData, and follow the links, I think you’ll see a pretty good case for why a per-gig pricing model is problematic, but the one thing you won’t see is what…

  • | |

    FUD, but not entirely

    Joe Wilcox does a good job of finding the FUD in Microsoft’s 10 reasons not to use Google Apps. I’d have to agree with him that Microsoft’s reasons are pretty dumb. One thing that does jump out at me though, is number 7: Enterprise companies have to constantly think about government regulations and standards?while Google…

  • In the news:

    So the government is pushing smart cards as a way to protect against terrorism, right? Well they should read this story, Smart-card security needs an upgrade. -seems those little wonders are easily hacked into. How nice would it be to have someone steal your smart card ID and have easy access to your identity? Microsoft…

  • |

    Another good newsletter

    Don’t remember if I’ve talked about this newsletter lately, but here are a few links that I will be looking at in more detail later from the latest issue of Tech Support Alert: Anti-Trojan Software Reviews ChimeNote -an alternative to emailing yourself reminders to/from different email accounts. Free Linux Desktop Guide for Non-Linux Users Qwik-Fix…

  • Major issues down..

    It’s 10AM and between putting in 4 hours yesterday and two so far today, all of the major issues left over from my vacation have been dealt with. My boss’ hard drive has been replaced and the software installations finished (except for the accounting package, she has always done that one herself) , the receptionist’s…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)