Google Encrypts to Evade NSA Surveillance: Should You?

 
 
By Sean Michael Kerner  |  Posted 2013-09-10 Email Print this article Print
 
 
 
 
 
 
 
surveillance

As Google ramps up its data-encryption efforts, now is a good time for enterprises to consider their own data-protection postures.

Revelations made public last week about alleged National Security Agency (NSA) capabilities for defeating Internet cryptography are having a ripple effect, causing companies big and small to re-evaluate their use of cryptography. One of those vendors is none other than Google.

According to a published report in The Washington Post, Google is accelerating its efforts to cryptographically secure data. Google's moves do not require any specific action from users as the activity is focused around encrypting data between Google's own data centers.

Google's actions are being praised by some and met with skepticism by others.

Carson Sweet, CEO and co-founder of CloudPassage, told eWEEK that in his view, Google's actions are a step in the right direction. "There's no way that Google can prevent snooping for every situation, but the level of investment they're making here is a big statement as to their commitment to customer privacy," Sweet said. "The unfortunate reality is that a government agency is no different from any other attacker seeking sensitive data; if one attack vector is severed, they will go to work looking for another one."

Geoff Webb, director of solution strategy at NetIQ, told eWEEK that Google's highly visible stance on the issue of data protection is not too surprising, as Google relies on trust from its consumers.

"However, while encrypting data will certainly hinder illegal hackers and potentially slow down untargeted data gathering by the NSA, the real question with encryption is—who has access to the keys?" Webb said. "If the NSA is able to gain access to the keys used to encrypt the data, then there is no additional privacy for users."

Carl Livitt, senior managing associate at security consultancy Bishop Fox, isn't quite as positive about Google's actions for a number of reasons. What Google is actually specifically doing with its new encryption is not yet publicly known, Livitt pointed out, adding that going a step further as a government agency, the NSA still has mechanisms that could allow it to get what it wants.

"If the NSA were to approach Google and demand access to their new encryption using a secret FISA [Foreign Intelligence Surveillance Act] court order, Google would be gagged from talking about it," Livitt said. "This leaves us right back at square one."

What Should Enterprises Do?

Regardless of what Google is doing to protect itself and its own customers, a good best practice for enterprises that CloudPassage's Sweet suggests is for organizations to take control of their own privacy.

"What the providers do is helpful, but at the end of the day, adding privacy technologies that you control is the best way to have assurance," Sweet said. "From the Google perspective, there are dozens of gApps add-ons that encrypt email, content, etc., and leave the keys in your control."

Bishop Fox's Livitt is somewhat more pessimistic about what users should or shouldn't use. Office365, Skype, Gmail, Yahoo Mail, Hotmail and Facebook are all compromised by the NSA, he said. "If this affects you, don't use those services," Livitt said.

Enterprises should assess their own risk—with the understanding that some data is more important than others—and  should take extra safeguards for critical information, Livitt said.

Those worried about government snooping should use their own infrastructure and avoid the cloud, Livitt said.

"If you must use the cloud, avoid U.S.-based cloud providers because you will never know if your data is being tapped—this is because of the secret FISA court orders and related gag orders," he said. "Do research into non-USA cloud providers, but avoid New Zealand, U.K., Australia and Canada; they are all working together with the NSA. If all of that fails, try wearing a tinfoil hat."

Sean Michael Kerner is a senior editor at eWEEK and InternetNews.com. Follow him on Twitter @TechJournalist.

 

 
 
 
 
 
 
 
 

5 Comments for "Google Encrypts to Evade NSA Surveillance: Should You?"

  • phloid domino September 13, 2013 4:36 pm

    the first comment (Vik James), while poorly reasoned based on incomplete understanding of certificates and ssl, nevertheless hits on one very important point, that links in the so-called 'chain of trust' can be compromised this is absolutely true, and has been shown to be true repeatedly in the last few years the management of certificates is broken, with too many implicitly trusted issuers built into common browsers, and yes, it does mostly rely on email and dns for basic verification of identity if you want to communicate securely, learn to use public/private keys to encrypt the content, and convey the public keys reliably between the parties to the communication even so, if a government wants to coerce one party into giving up a key, it can, but at least you can be secure against dragnet surveillence and most hackers

  • Anonymous September 13, 2013 1:29 pm

    The goal is not to block the NSA on decrypting a specific message. They will find a way. The goal is to overload their data centers such that they have to go back to the constitutional mandate of only decrypting those they for which the get a warrant.

  • Vik James September 12, 2013 2:02 pm

    But to get an encryption certificate, it is required to apply to a USA based security company using plain test email and provide them with the keys to our private web site before they can provide the SSL certificate. Any agency looking at internet traffic will be able to see the application for an encryption certificate and keep a copy of our key for their own purposes. HTTPS and SSL is an illusion of security with no reality - the keys can be intercepted when any application is made.

    • natas September 12, 2013 11:36 pm

      lol, do you know how certs works? If you make a cert request and then send it you will NOT sending out your private key, but the public. Time to study asymetric cryptography. But you are right that PKI CA is illusion - you are depending on a few links in a chain of trust, that can be compromised by NSA or any other motivated attacker. Or you can simply be a victim of (planned) vulnerability of concrete crypto implementation.

  • David Allen September 11, 2013 5:51 am

    I used to think that it was necessary for me to encrypt anything because I don't do anything that is bad and really requires encryption. I know how to use GPG open source public encryption and for things that are private and I have to be sent by email and so I will send those encrypted and signed. So the fact that I'm not doing anything bad at the moment, doesn't mean that the rules can't be changed and something could be made illegal at a later stage. With this in mind, it could be a good idea now to think about encrypting everything as a matter of course. Signing and encrypting everything in terms of doing one or the other, then I think it is better to have one way of working. It is just so much easier to have one policy for Internet communications and sound better to her on the side of caution.

Leave a Comment

 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel