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.'"
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.
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!
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.
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"
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.
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
You can't search in an encrypted file. With a stream cipher, the ciphertext results are context dependent. Even if I encrypt the search term with the same key, I won't find it in the ciphertext. Google would have to decrypt back to plaintext to do the search.
So, Google has your data, and Google can lose your data. Or else Google can't search your data -- in which case what's the point?
Blocking desktopservices.google.com effectively breaks the search across computers function, but it also breaks some other functions in the google sidebar - such as rss news feeds. Of course blocking this at the proxy is only effective while the user is in your network. Once they take their laptop home...
It's sad that windoze users have to go and ask how to NOT install programs. If the OS were as secure as their "Trustworthy Computing Initiative" was full of crap the users would always be asking "How do I install programs". Why are end users installing stuff to begin with? Here's a rule of thumb....for every app they install on purpose, they have 10 malicious apps that are installed without their knowledge that evade the "science" of spyware and virus scans. Honestly....
" 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."
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.