Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Privacy Encryption Google Government

How Big Companies Can Hamper the Surveillance Infrastructure 153

Trailrunner7 writes "Buried underneath the ever-growing pile of information about the mass surveillance methods of the NSA is a small but significant undercurrent of change that's being driven by the anger and resentment of the large tech companies that the agency has used as tools in its collection programs. The changes have been happening since almost the minute the first documents began leaking out of Fort Meade in June. When the NSA's PRISM program was revealed this summer, it implicated some of the larger companies in the industry as apparently willing partners in a system that gave the agency 'direct access' to their servers. Officials at Google, Yahoo and others quickly denied that this was the case, saying they knew of no such program and didn't provide access to their servers to anyone and only complied with court orders. More recent revelations have shown that the NSA has been tapping the links between the data centers run by Google and Yahoo, links that were unencrypted. That revelation led a pair of Google security engineers to post some rather emphatic thoughts on the NSA's infiltration of their networks. It also spurred Google to accelerate projects to encrypt the data flowing between its data centers. These are some of the clearer signs yet that these companies have reached a point where they're no longer willing to be participants, witting or otherwise, in the NSA's surveillance programs."
This discussion has been archived. No new comments can be posted.

How Big Companies Can Hamper the Surveillance Infrastructure

Comments Filter:
  • by ameline ( 771895 ) <ian.ameline@Nospam.gmail.com> on Saturday November 16, 2013 @07:00PM (#45445271) Homepage Journal

    They aren't getting *nearly* paranoid enough. They should be encrypting the data on disk, on network connections between machines in the *same* data center, not just between centers. In fact the data should remain encrypted at all times unless absolutely necessary to have in clear-text to process it -- and that should never leave the CPU. It should remain clear-text only for the absolutely minimum time required.

    They should assume that hostile agencies (foreign *and* domestic) have tapped every last network link they own. As well as most routers and processing machines. They should also assume that some small percentage of their workforce are working on behalf of one of these adversaries. Given these assumptions they should design a system that can remain as secure as possible given these circumstances.

    Merely encrypting the network links between their data centers is not nearly enough to thwart the likes of the NSA, CSEC, GCHQ or other nameless agencies.

  • by Teun ( 17872 ) on Saturday November 16, 2013 @07:59PM (#45445485)
    Not only the big boys beef up their security, even Kubuntuforums.org has today enabled https access.

    Encrypting by the big players is significant, the data streams between their centers effectively mirrors all they have, from the POV of the government sanctioned goons it is about as good as you're going to get without the need to physically enter the server rooms.

    A small forum is obviously not using a secure connection to hide their data but instead it's meant to secure the login process.
    Yet it shows not only the big enterprises are able to improve security and especially the privacy of their users

  • by swillden ( 191260 ) <shawn-ds@willden.org> on Sunday November 17, 2013 @01:14AM (#45446721) Journal

    Dude, I really wish I could give you a point by point response. Actually, I typed one out, and then realized that I went too far. I personally think Google is making a big mistake by not being more open about its security policies, procedures and technologies -- because they're awesome -- but the fact is that a lot of it is confidential, and I like my job.

    What I will tell you is this: Google's general solution to cross-DC traffic wasn't to add link-level encryption to the cross-DC links, and there is so much cross-DC traffic that it would be a nightmare to try to identify the cross-DC connections and encrypt just them. Further, stuff gets shifted around between DCs a lot, so any such solution would be beyond brittle. I'll let you extrapolate from there.

    The other thing I'll say is just to give you a testimonial of sorts. You take it with however much salt you want... and I guarantee I'm going to get a bunch of foul-mouthed ACs (and maybe even non-anonymous cowards) calling me all sorts of variations of "liar". Whatever.

    I was an IBM security consultant for many years. I spent a lot of time working in the bowels of the security infrastructure of a lot of big companies, and even some governmental organizations -- including some military organizations. I was also a security policeman in the US Air Force in a previous life (long story), so I have a pretty solid grounding in physical security, not just infosec. One of my degrees is in mathematics, and I was fascinated with cryptography from an early age, so much of my independent study during my degree was around crypto, and I continued my self-education and practical education afterward (which is how I ended up as a security consultant).

    My point? I know more than a little about security, and I've seen a lot of what passes for security in both government and industry, including in organizations that handle a lot of sensitive data and really should know how to secure it.

    Google is better at it than any of them. Head and shoulders.

    Perfect? No. Nothing is perfect. But Google has world-class security talent, a lot of it, and Google's engineers have always cared a lot about security... and are now angry as well.

    Anyway, take that for whatever you want, but it's my absolutely honest opinion. Google can do a hell of a lot to obstruct the NSA's illicit snooping, and intends to do everything feasible.

    (Disclaimer: I work for Google, but I don't speak for them and they don't speak for me.)

  • by swillden ( 191260 ) <shawn-ds@willden.org> on Sunday November 17, 2013 @01:30AM (#45446763) Journal

    Encrypting is useful, but then comes the very nasty thing that comes with it: Key management.

    Google has an outstanding key management infrastructure. That problem was actually already thoroughly solved a while ago. Actually, it's pretty well-solved outside of Google as well, for point-to-point links within an enterprise. Kerberos (though Google's solution is more robust than Kerberos).

    Oh, the CA keys. Are they stashed in an armored HSM

    Google has a great answer there, too. I wish I could share it.

  • Re:Outsource freedom (Score:4, Interesting)

    by erikkemperman ( 252014 ) on Sunday November 17, 2013 @08:56AM (#45447797)

    The famous Swiss banking privacy isn't what it used to be.

    The US Gov. (and others) has had teams of people working on special "Switzerland policies" for decades.

    Which, as I understood it, might be part of the reason they apparently want to branch out from banking. Still backed by some of the same strict privacy laws which allowed anonymous banking to flourish, even if that is now drying up slightly, they might well succeed in setting up what amounts to a data haven.

    Of course it won't be very long until the various spooks will try and eventually no doubt succeed at infiltrating and subverting that in the same they have been doing to Swiss banks.

    It was one of these operations (CIA, I believe, getting a banker drunk behind the wheel with the aim of blackmail) that appalled Snowden in particular while he was stationed thereabouts.

    In a weird way we'll have come full circle if one result of all this would be a data haven in Switzerland.

One man's constant is another man's variable. -- A.J. Perlis

Working...