Slashdot Mirror


Google Copies Corporate Data to Google's Servers?

Penguinisto writes "According to Silicon.com, some CIOs have been seeing their company data being transferred to Google's servers as part of Google Desktop's functionality." From the article: "Mark Saysell, IT director at Coutts Retail Communications UK, said he is planning a network audit to find rogue installations, which will then be de-installed. New security measures will also be put in place to prevent further downloads. He said: 'Google has definitely over-stepped the mark and in turn is forcing IT departments to take a very draconian approach to machine security and web access.'"

48 of 295 comments (clear)

  1. more sensationalism by jbellis · · Score: 4, Informative

    This article is a joke. It's all about quoting people talking about how dangerous the new version of Google Desktop is when Google is very up-front about telling you what features will result in data being copied, and how to turn it off.

    IT'S DISABLED BY DEFAULT. You have to WANT to turn it on.

    Lousy reporting, is what this is.

    1. Re:more sensationalism by saleenS281 · · Score: 2, Interesting

      And... how are they to prevent employee's who WANT to turn it on from doing so? Just because THEY don't want it turned on doesn't mean they have any control over whether or not EMPLOYEE'S turn it on.

    2. Re:more sensationalism by Reality+Master+101 · · Score: 4, Insightful
      This article is a joke. It's all about quoting people talking about how dangerous the new version of Google Desktop is when Google is very up-front about telling you what features will result in data being copied, and how to turn it off. IT'S DISABLED BY DEFAULT. You have to WANT to turn it on.

      I see you've never worked in customer support. Rule #1: People f*** with stuff. If there's a way for users to screw things up, then users WILL screw things up. All it takes is one secretary in the wrong position to flip the switch and suddenly you have Ubersecret Documents flying out of your not-as-secure-as-you-thought network. Sure, I doubt Google is going to spray your documents all over the web, but if I was a CIO whose entire livelihood depending on locking down the network of a multi-billion dollar company, I wouldn't want this thing on my desktops, either. The "neat-o" functionality provided just isn't worth the risk that someone might sniff out the data somewhere in the chain.

      --
      Sometimes it's best to just let stupid people be stupid.
    3. Re:more sensationalism by duffbeer703 · · Score: 2, Insightful

      When one of your bank's employees decides that he WANTS to "share" your personal data with his home PC, don't bitch.

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
    4. Re:more sensationalism by Knight+Thrasher · · Score: 4, Insightful
      At that point Google Desktop would be more of a tool, and it would fall more on the employees shoulders for responsibility.

      If I install a FTP server app on my computer at work, set it to allow anonymous and share my whole hard drive, that's my fault when feces meets oscillating blades.

    5. Re:more sensationalism by jibjibjib · · Score: 3, Insightful

      If they're trying to stop employees *deliberately* getting their data copied to other servers, they would need to block internet access altogether. On its own, banning Google Desktop would not help to stop people who actually want to send data to places.
      There is a possibility that someone might not understand what they're doing, and accidentally enable this option, but similar possibilities exist with any Internet software, so there's no reason to single out Google Desktop specifically in this case.

    6. Re:more sensationalism by g0at · · Score: 2, Insightful

      This article is a joke.

      Zonk posted the article. Just like the completely misleadingly-excerpted Apple one earlier. Are you surprised?

      -b

    7. Re:more sensationalism by jdgreen7 · · Score: 2, Insightful
      Normally, I would agree with you. But, seeing as how the Google Toolbar is now included with the latest Sun JVM (even when simply doing their "security updates", you have to manually uncheck the option to download that tool), I'm getting a little leary of the Google monster. It's one thing to offer a service to someone as an option, but quite another to bundle your service with unrelated options as part of "security updates".

      Who's to say that Google some day won't decide to enable this feature by default in the future as part of their own security upgrade? We've finally taken the stance of not allowing employees to install ANYTHING on their PCs anymore as a result of such bundling in addition to more and more spyware crap recently. A little more work for us in some aspects, but I think it will save us down the road.

    8. Re:more sensationalism by AusIV · · Score: 3, Insightful
      So Google shouldn't create a useful tool because it might be abused? There are plenty of ways that employees can share data that employers would have a hard time stopping, but every one of them is deliberate. If an employee is sharing data they shouldn't be sharing, that's the employee's fault, not Google's.

      From a networking standpoint, Google Desktop is as easy to block as any other protocol. I have no problem with companies banning Google desktop on their systems, but isn't it a bit extreme to say Google shouldn't have made a product that many people are using quite productively, just because they have to take efforts after their own employees abuse it?

    9. Re:more sensationalism by Rolan · · Score: 4, Insightful
      Well...isn't that what this article is about? Sounds like you agree with the CIOs.

      Not really. The CIOs in the article are saying that it shouldn't be installed at all. What I'm saying is that the product itself is not "harmful", but simply a feature of the product that is turned off by default. So, there's no problem with allowing people to use the product, so long as they do not turn on the feature. The policy you write is that the feature can not be enabled, and that is what you audit.

      If Google wanted to deflect this criticizm even more, they'd do a bit of extra code to allow Group Policy to disable the feature and keep users from enabling it. However, there's not much to criticize about it in the first place. It clearly states what happens if you turn on the feature (some files are stored on Google's Servers) and the feature is off by default. People who turn it on know what they're getting into here; it is very clear. If corporate IT/CIOs have problems with their users, then it is the user to blame, not the software feature.

      This is like saying that Microsoft has overstepped the bounds by installing solitare and other games with Windows XP Pro, because it would be harmful to productivity.... The software's not the problem, the user is.

      --
      - AMW
    10. Re:more sensationalism by testrake · · Score: 4, Informative

      Perhaps "they" do a little research and determine that you can use GPO to disable the parts they don't want running?

      They can, in fact, disable the installation in at least two ways: GPO from Microsoft (Google for "Software Restriction Policy") OR GPO from Google (http://desktop.google.com/enterprise/index.html)

      The GPO from Google (part of the Enterprise download) is able to control many of the settings -- including the sharing of index data and encryption of the indexes -- on both the Enterprise Google Desktop and standard Google Desktop.

      Of course, a competent network administrator would already know that, right?

    11. Re:more sensationalism by rtb61 · · Score: 4, Insightful
      Actually the whole story doesn't make any sense at all. Employees at large companies installing what ever software they feel like. These people don't need to be worrying about Google desktop search they need to be installing Linux desktops now and taking control over the corporate desktop and software environment.

      If anything goes wrong in IT at a company it is the IT departments fault, they choose the software, they choose the hardware and they implement both. Network and computer security is the IT departments responsibility and yes I know a lot of companies tend to treat security as a joke until there is a major failure, then blame the IT department.

      This story is just another M$ beat up and doesn't relate to Google at all, it is really about the typical dysfunctionality of M$ windows and the difficulties in securing it properly whilst allowing users to make use of software on their computers with out being forced to allow them administrator access.

      --
      Chaos - everything, everywhere, everywhen
  2. This is dumb by Danse · · Score: 3, Insightful

    If CIOs don't want people using Google Desktop, then make it a policy that they should not use it. Enforce the policy. End of story. Don't blame Google for making a tool that a lot of people find useful. There are other ways to give your enterprise the same capabilities without compromising your data.

    --
    It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
  3. Re:CIOs, come on, go(ogle) for it! by larien · · Score: 4, Interesting
    It really depends on the data...

    I work in a bank and while I don't have files relating to customer information on my PC, I'm pretty sure I'd contravene some kind of law if I were to install Google Search & some files were transferred to Google. If I did have customer files, I'm almost certain some law would be broken if those files were sent to Google.

    If CIOs or others want the kind of functionality & productivity that Google desktop search can provide, let Google sell local servers (same as they do for web search engines) so these companies can buy them and get the tools that way without the data ever leaving their networks & control.

  4. Re:CIOs, come on, go(ogle) for it! by saleenS281 · · Score: 3, Insightful

    Except, as we've seen, even the great google has software vulnerabilties. Whether they are trying to be good citizens is irrelevant. What happens when hackerX finds a hole and has access to * corporations NDA type information. I know I'd rather have it stored away on an internal server behind a vpn and several firewalls with IP based filtering than on google's network, but that's just me.

  5. Re:CIOs, come on, go(ogle) for it! by Knight+Thrasher · · Score: 2, Insightful

    You;re forgetting crucial items, such as payroll and customer information like personal info and credit card info, for example. These two things alone would convince me to lock down my workplace from using Google Desktop. That is data I don't want easily distributed in any fashion.

  6. That explains everything... by __aaclcg7560 · · Score: 2, Funny

    ... CIOs have been seeing their company data being transferred to Google's servers ...

    No wonder Google doesn't want to cooperate with the Justice Department's request for information. They're running warez servers!

  7. Re:CIOs, come on, go(ogle) for it! by OverlordQ · · Score: 2, Interesting

    I still submit they honor their "do no evil" credo.

    Do No Evil Unless It's A Good Business Action

    re: China

    --
    Your hair look like poop, Bob! - Wanker.
  8. Not googles fault by The+Mysterious+X · · Score: 4, Insightful

    This isn't an issue with google. It's an issue with the users.

    Search across computers is disabled by default. It doesn't even ask you to enable it in the intaller. You have to hunt through the options to turn it on.

    It's not google "overstepping the mark" it's incompetant users changing settings they don't understand.

    On a different note, if I were a sysadmin, then I would not be letting them install GDS anyway, without authorisation. They are company machines, subject to company rules, and should only run company software.

  9. snort signatures for network admins by farker+haiku · · Score: 2, Informative

    Snort signatures for the google desktop and download of google desktop can be found here.

    If you're really worried.

    --
    Your sig(k) has been stolen. There is a puff of smoke!
  10. IT Maintaining Software by ThePepe · · Score: 3, Insightful

    Is it really asking too much of an Admin to maintain good software installation permissions and policies? If untrustworthy users have been given high enough authority to install their own software then Admins have no one to blame but themselves.

    Well you can probably blame management too.. thats always good.

  11. Re:CIOs, come on, go(ogle) for it! by duffbeer703 · · Score: 2, Interesting

    Are you nuts? The spreadsheet on your desktop might contain important customer data, sensitive personal communication, or god knows work. And Google is taking it upon itself to upload it, unencrypted, over the internet.

    And uploading my data to a server controlled by a company that employs some of the most talented people in data mining is just asking for trouble.

    --
    Conformity is the jailer of freedom and enemy of growth. -JFK
  12. From a healthcare perspective by PIPBoy3000 · · Score: 3, Informative

    There are certain laws in place that regulate how confidential patient information is passed around (HIPPA). I'm fairly certain that should an employee have such information on their desktop and it's copied up to Google, that would constitute a breach of those laws.

    Because of this, our desktop folks have decided that Google Desktop is not something that can be installed. It's a shame, too, as there's lots of "benign" features that we miss out on because of it.

  13. Doing what it's designed to do by Todd+Knarr · · Score: 4, Insightful

    Google Desktop is doing what it's designed to do: keep user's data on central servers so it's accessible from anywhere. It's just that it makes the assumption that all of the computer belongs to the user. Obviously in a corporate environment that's not the case, but Google Desktop doesn't know what kind of computer it's on so it can't do anything about that. The company needs to be more emphatic about the "no unauthorized software" rule (they do have a "no unauthorized software" rule, don't they?).

  14. google value by woverly · · Score: 4, Insightful

    This is where Google's greatest value really lies: data mining. The possible advertising revenue pales in comparison to the value of the corporate (and even consumer) intelligence that Google collects. Simply being able to detect that persons in company x are suddenly interested in company y and that investment bank z is also interested in company y would allow one to predict things like mergers. Increased specific searches around the holidays might help predict which retail chain might do well. The power of Google should not be underestimated.

    --
    Woverly Harris Gooch, IV CTO American Fire and Bomb, LLC
  15. Easy solution by GmAz · · Score: 2, Insightful

    Tell your employees not to install the software. Its not that hard. And if the employee does install it, hold that person liable for the data transfered.

    --
    Click Click Bloody Click PANCAKES!
  16. These CIOs should also by moria · · Score: 2, Insightful

    They should also forbid/filter HTTP POST requests, IM file transfers, e-mail attachments, and any internet application that would allow the enterprise data to flow out of the company network.

    This style of ruling totoally miss the point. You should teach your employers to generally avoid leaking enterprise data out of the company network and the risks of using certain applications. It is not to disable or to forbid the use of certain programs. Google Desktop Search is not built to compromise your data security, especially when this contradictionary function is turned off by default. It is your disloyal employer who you should be careful about. Your employ will always find a way if he wants to leak the enterprise data.

  17. Google has Overstepped the mark? by logicnazi · · Score: 2, Insightful

    By doing what? Releasing a software package which does exactly what it says it does?

    Might as well say the people who wrote FTP overstepped the mark as it doesn't stop people from sending sensitive data outside the company.

    --

    If you liked this thought maybe you would find my blog nice too:

  18. Here's what's dumb by fm6 · · Score: 4, Insightful
    Which is exactly what the CIO did. What's dumb is that Google (allegedly) got careless about copying data, putting the CIO in the position of having to ban the program. And what's absolutely stupid is idiots like you insisting that it's no big deal, just because nobody's forced to use the product. That's like saying that exploding laptops are no problem, just because only some brands explode.

    I use Google desktop, and find it very handy. It's quite possible I'll have to give up using it because of this issue. That doesn't make me feel well-disposed towards Google, or inclined to try any new products they might release.

  19. WTF?! by d34thm0nk3y · · Score: 3, Insightful

    If these people have such sensitive data on their machines why the hell are they allowed to install any random software off the web onto them?? You can get "software" that does waaaaaaay more than just cache some of your files online, and you might not even know you installed it.

  20. Google doesn't understand corporate IT by Anonymous Coward · · Score: 4, Insightful

    It seems to me that Google is in the same position that Microsoft was years ago, when corporations all ran Netware or IBM servers because Microsoft products were naive about corporate reqirements. Google will probably climb the learning curve faster than Microsoft did, but they aren't there yet. /. readers who make suggestions like "forbid installing the software" or "fire users who do it" also don't understand corporate IT. Some corporations have desktops locked down so users can't install software, but some don't because their users are higher level and need to install selected applications.

    The suggestion to fire users who turn on the data upload is also hated by IT managers. Corporations are full of clerks and other mid-level people who never read IT policy documents, don't really care about security, and like to turn on cool features. The IT manager is not going to look good if he tells HR "Sally who is otherwise a great employee checked this box because she didn't know she shouldn't, so now you have to fire her".

    IT managers differ, but they generally want to give users as much functionality as possible, as long as they are sure it is safe and reliable. What an IT manager probably wants are network-level options to (1) forbid Google desktop entirely, (2) allow it but disable the data-sharing features, (3) leave it up to the user, or (4) do a mandatory (push) install to all desktops. Then the IT manager would want a web page or other report to see who had done what.

    When Microsoft figured out requirements like these, they invented Active Directory and its Group Policy component. Look at products like Symantec Antivirus Corporate, where you can look at all desktops and verify their antivirus status from a central console, or Microsoft's own free WSUS which lets you make sure everybody in the corporation has installed all critical patches.

    These are the kinds of solutions that work in the real world as opposed to firing people, and as soon as Google figures this out they will be a lot more popular on corporate desktops.

  21. Blaming Google is Bullshit by richg74 · · Score: 4, Insightful
    From TFA:
    $ORGANIZATION is about to update its information security policy in light of Google Desktop with a recommendation that the software must not be downloaded onto any ... PC.

    For heaven's sake, what planet do these people that are allegedly responsible for IT come from? Let's see:

    1. Express great concern for security of secret corporate data
    2. Allow users to install software on their PCs
    3. Express shock and outrage that potential security problems develop
    4. Blame Google !

    I've worked as an IT director in a few financial services companies over the last ~20 years, and everyone employed there, on their first day, had to read and sign something like this:

    I understand that computer equipment and facilities provided to me are the property of the Company, and are to be used only for permitted business purposes, as outlined in the Computer Use Guidelines. In particular, I understand that unauthorized removal of Company data from the premises, or installing or downloading software from any unapproved source, are grounds for immediate termination. I acknowledge receipt of a copy of the Computer Use Guidelines.
    We would install or make available external software if it was useful and appropriate, after testing it. Otherwise, no dice. Will some people complain? Absolutely! Tough shit.
  22. Why Doesn't Google Do It Right? by severoon · · Score: 4, Insightful

    I'm confused...google could have its cake and eat it too if they did this feature right.

    Here's how it ought to work. Everything is encrypted client-side before being sent up to the google servers in a way that google can't decrypt based on your user account password guarding public/private keys you generate per machine in the GDS front-end. Only the public keys are shared across the network, the data is completely encrypted everywhere except the endpoints. What's the problem?

    Ah ha!, you say, the problem is that they mine that data on their servers for information they can use to advertise at you. First, is this true? I haven't been able to confirm it, though it seems in line with their advertising model. Second, assuming it is true, there's no reason GDS can't create some kind of index over your data client-side and then send up the statistical summary of the info it mined. That way, there's no way the docs could be reconstructed, google gets their ad revenue, and users get their functionality without having to worry about data on google's servers.

    Anyone have any notion of why this wouldn't work?

    --
    but have you considered the following argument: shut up.
  23. How about a version without upload? by DotDotSlasher · · Score: 4, Interesting

    My company now forbids using Google Desktop because of this feature.
    Yes, it's off by default.
    Yes, you have to go out of your way to turn it on.
    Yes, they keep track of what's installed on everyone's machine.
    Yes, there are ways around that -- but for safety's sake, I now use MSN's local search.
    Google's product is forbidden.

    So google (you listening?) -- how about local-only version for us corporate folks, with the upload option completely removed?
    We get a version that can be blessed by IT, you keep your user base.
    Seems like a winner to me.

  24. Microsoft: Different Tune? You bet! by Saeed+al-Sahaf · · Score: 4, Insightful
    This isn't an issue with google. It's an issue with the users.

    If this had been a Microsoft product, the tune here would be different. Much different.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Microsoft: Different Tune? You bet! by mandos · · Score: 2, Interesting

      That's because they'd integrate it with a product that you already have, change the terms of service and force a mandatory update. Whereas with the Google product it's a software addon to your computer experince and you have to go download it yourself. It doesn't come preinstalled on 90% of computers.

      --
      Mike Scanlon
    2. Re:Microsoft: Different Tune? You bet! by rob_squared · · Score: 3, Insightful

      Well, the windows equivalent is file sharing, and that's off by default too. And if it got turned on I'd blame the user, because they would have had to do it.

      Parent Moderation -1: False logic.

      --
      I don't get it.
  25. Re:Also depends on the law by networkBoy · · Score: 2, Funny

    "The first person who gets kidnapped because their financial data was copied by Google and then accidentally leaked by the secret service will not be happy."

    I submit to you that the second and third people this happens to will also be unhappy.
    The fourth, however will be thrilled to death, (as a result of his kids not paying the bounty).

    -nB

    --
    whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
  26. Re:CIOs, come on, go(ogle) for it! by Red+Alastor · · Score: 4, Informative
    On the other hand, Google Desktop should definitely default to not storing your data on anyone else's server.
    It is disabled by default. You can check the options during the install but it's clearly written that your files will be transfered to their servers. Of course people can't read but that's not Google's fault.

    But maybe they should default to disabled and not offer the choice during install. Just put it somewhere in the preferences where people who can't read won't go.

    --
    Slashdot anagrams to "Sad Sloth"
  27. Rule of thumb by Anonymous Coward · · Score: 2, Insightful

    If in order to make your point you have to make up an imaginary viewpoint that would occur under an imaginary situation, and then accuse other people of holding that imaginary viewpoint under your imaginary situation...

    You don't have a point at all.

  28. Google provided a way to disable it, corporate-wid by Truist · · Score: 5, Informative

    It took a bit to dig this up, but it turns out that if you set the registry key:

    HKLM\Software\Policies\Google\Google Desktop\Enterprise -> disallow_ssd_service

    as a REG_DWORD to '1'

    Google Desktop won't let you use the "Search Across Computers" feature. (I tried it.) You can set that key in the group policy scripts relatively easily.

  29. An idea for the next revision! by MrJynxx · · Score: 2, Informative

    How about this. Why doesn't google pick some obscure port for getting this data, make it public, and if the corp security guys want to stop the google copy, block the port on the F/W, problem solved!!!!

    MrJynxx

  30. Oh So Moronic by PacketScan · · Score: 2, Insightful

    "He said: 'Google has definitely over-stepped the mark and in turn is forcing IT departments to take a very draconian approach to machine security and web access.'" My favorite part of the story.. Draconain eh? why was the install allowed in the first place? Ever hear of group policy?

  31. Re:CIOs, come on, go(ogle) for it! by tftp · · Score: 3, Insightful
    There are 100 careless people for each crooked one. Your bank's CIO may have a policy of strong passwords, fingerprint authentication and such, but how will that help if Mary the teller sets up her Google account 'MarySmith' with password 'mary' ?

    This is the crucial difference between shooting someone into the heart vs. letting a careless person to borrow your handgun. In former case you do the deed. In latter case you set up the trap and wait until someone falls in. You don't even care who, as long as enough people enable this feature. In a large company 999 employees may be wise, but it takes only one stupid secretary to publish the whole company's network shares that she can read - and Google says that they can't promise that the data - any data - will be ever fully deleted. Technically that might be true (due to backups, distributed storage, etc.)

  32. Re:CIOs, come on, go(ogle) for it! by KDR_11k · · Score: 2, Insightful

    Microsoft doesn't copy local files to their server.

    --
    Justice is the sheep getting arrested while an impartial judge declares the vote void.
  33. Re:Google provided a way to disable it, corporate- by Sven+Tuerpe · · Score: 2, Insightful
    It took a bit to dig this up, but it turns out that if you set the registry key ...

    If they really do not want to be evil, they should:

    • Provide security documentation, and make it easily accessible to everyone (as opposed to "hard to dig up"). Security documentations means a detailed and complete description of what the software does, how it communicates, and how to prevent it from doing what the operator of a machine or network might not want it to do.
    • Offer multiple documented ways in which typical security policies could be enforced. For instance there should be an alternative for situations where group policies aren't an option, like communicating with Google's servers in such a way that perimeter filtering (read: firewall rules) can easily be used to suppress communications.
    • Make sure that the administrators of a network remain in control over individual functions and services. Enforcement of a security policy, in whichever way it may be implemented, should not have side effects on other services. It should not be necessary e.g. to block all Google access or to route all Web access through a mandatory proxy in order to suppress one particular function of Google Desktop.

    In other words, I would like to see Google Desktop use e.g. a specific source and/or destination port that can be blocked at packet filter level, and I would like to see this documented. I haven't verified whether it does so already, though.

    --
    http://erichsieht.wordpress.com/category/english/
  34. Yes, I dealt with this last week. by ninja_assault_kitten · · Score: 2, Interesting

    I actually sent out communication to our employees last week requiring users to disable the "Search Across Computers" functionality (which we're monitoring) rather than requiring them to remove it completely. Additionally, I have the Windows administrators investigating the possibility of using the GDS Enterprise solution, which has full AD support and the ability to disable Search Across Computers through Group Policy.

  35. Re:Google provided a way to disable it, corporate- by Truist · · Score: 3, Informative

    There is an Enterprise version of Google Desktop that you ask for, except maybe #2. But I don't think they use a specific port - I assume it's all web service-based.

    The 'hard to dig up' bit was because I had to download their Enterprise version, read its documentation, and interpret the Group Policy Template to figure out what the registry key was. If it was actually trying to roll something out company-wide they've gone to great lengths to make it easy.