Recommended Posts

Data Harvesting at Google Not a Rogue Act, Report Finds

SAN FRANCISCO ? Google?s harvesting of e-mails, passwords and other sensitive personal information from unsuspecting households in the United States and around the world was neither a mistake nor the work of a rogue engineer, as the company long maintained, but a program that supervisors knew about, according to new details from the full text of a regulatory report.

The report, prepared by the Federal Communications Commission after a 17-month investigation of Google?s Street View project, was released, heavily redacted, two weeks ago. Although it found that Google had not violated any laws, the agency said Google had obstructed the inquiry and fined the company $25,000.

On Saturday, Google released a version of the report with only employees? names redacted.

The full version draws a portrait of a company where an engineer can easily embark on a project to gather personal e-mails and Web searches of potentially hundreds of millions of people as part of his or her unscheduled work time, and where privacy concerns are shrugged off.

The so-called payload data was secretly collected between 2007 and 2010 as part of Street View, a project to photograph streetscapes over much of the civilized world. When the program was being designed, the report says, it included the following ?to do? item: ?Discuss privacy considerations with Product Counsel.?

?That never occurred,? the report says.

Google says the data collection was legal. But when regulators asked to see what had been collected, Google refused, the report says, saying it might break privacy and wiretapping laws if it shared the material.

A Google spokeswoman said Saturday that the company had much stricter privacy controls than it used to, in part because of the Street View controversy. She expressed the hope that with the release of the full report, ?we can now put this matter behind us.?

Ever since information about the secret data collection first began to emerge two years ago, Google has portrayed it as the mistakes of an unauthorized engineer operating on his own and stressed that the data was never used in any Google product.

The report, quoting the engineer?s original proposal, gives a somewhat different impression. The data, the engineer wrote, would ?be analyzed offline for use in other initiatives.? Google says this was never done.

The report, which was first published in its unredacted form by The Los Angeles Times, also states that the engineer, who began the project as part of his ?20 percent? time that Google gives employees to do work on their own initiative, ?specifically told two engineers working on the project, including a senior manager, about collecting payload data.?

As early as 2007, the report says, Street View engineers had ?wide access? to the plan to collect payload data. Five engineers tested the Street View code, a sixth reviewed it line by line, and a seventh also worked on it, the report says.

Privacy advocates said the full report put Google in a bad light.

?Google?s rogue engineer scenario collapses in light of the fact that others were aware of the project and did not object,? said Marc Rotenberg, executive director of the Electronic Privacy Information Center. ?This is what happens in the absence of enforcement and the absence of regulation.?

The Street View program used special cars outfitted with cameras. Google first said it was just photographing streets and did not disclose that it was collecting Internet communications called payload data, transmitted over Wi-Fi networks, until May 2010, when it was confronted by German regulators.

Eventually, it was forced to reveal that the information it had collected could include the full text of e-mails, sites visited and other data.

Even if a user was not working on a computer at the moment the Street View car slowly passed, if the device was on and the network was unencrypted, all sorts of information about what the user had been doing could be scooped up, data experts say.

?So how did this happen? Quite simply, it was a mistake,? a Google executive wrote on a company blog in 2010. ?The project leaders did not want, and had no intention of using, payload data.?

But according to the report, the engineer suggested in his proposal that it was entirely intentional: ?We are logging user traffic along with sufficient data to precisely triangulate their position at a given time, along with information about what they were doing.?

Attending to paperwork did not seem to be a high priority, however. Managers of the Street View project told F.C.C. investigators that they never read the engineer?s proposal, called a design document. A senior manager of Street View said he ?preapproved? the document before it was written.

More than a dozen countries began investigations of Street View in 2010. In the United States, the Justice Department, the Federal Trade Commission, state attorneys general and the F.C.C. looked into the matter.

The engineer at the center of the project cited the Fifth Amendment protection against self-incrimination. Because F.C.C. investigators could not interview him, they said there were still unresolved questions about the case.

Source: The New York Times

Whatever happened to 'Don't be evil.'?

I don't think that the engineers realised the privacy implications with the raw dataset at the time. To them all they saw was a lump of raw data which they would have access to when they drive by anyway, without realising that there is sensitive information that is transmitted unencrypted (To a computer science engineer, their natural instinct is that all sensitive information would be encrypted if it truly was sensitive, even if this is not the reality in this imperfect world). To them it was just the data acquisition phase for them to work out which useful data they need later. They are right to have concerns about sharing it, because when they acquired it they did not see any malicious uses but when it was later realised that it could be used maliciously, they wanted to do the right thing which is to destroy it and not give it to interested parties who may have an interest in using it for malicious purposes. From the perspective of a computer engineer who can see how this could have easily happened when left to a bunch of engineers (I imagine that the idea went along the lines of "lets just run kismet and see what we can get for our maps" not "lets run kismet and see what private information we can steal so we can run some identity theft on the side"), I fail to see the evil.

I don't think that the engineers realised the privacy implications with the raw dataset at the time. To them all they saw was a lump of raw data which they would have access to when they drive by anyway, without realising that there is sensitive information that is transmitted unencrypted (To a computer science engineer, their natural instinct is that all sensitive information would be encrypted if it truly was sensitive, even if this is not the reality in this imperfect world). To them it was just the data acquisition phase for them to work out which useful data they need later. They are right to have concerns about sharing it, because when they acquired it they did not see any malicious uses but when it was later realised that it could be used maliciously, they wanted to do the right thing which is to destroy it and not give it to interested parties who may have an interest in using it for malicious purposes. From the perspective of a computer engineer who can see how this could have easily happened when left to a bunch of engineers (I imagine that the idea went along the lines of "lets just run kismet and see what we can get for our maps" not "lets run kismet and see what private information we can steal so we can run some identity theft on the side"), I fail to see the evil.

Just give up, no matter how rational and competent reason you have, even the correct one will matter, this is just more fodder for the set of morons that hate Google and everything they do, and we will of course be called fanboys for not hating

This topic is now closed to further replies.
  • Posts

    • iPhone 18 Pro drop-test video and photos leak on the dark web following a data breach by Hamid Ganji iPhone 17 Pro - Image via Apple Apple is seemingly facing one of the biggest data breaches in its history, and just a few months before the official debut of the iPhone 18 Pro series, photos, a drop-test video, a supplier list, and key phone components have reportedly been leaked by hackers. Last week, we reported that Tata Electronics, an Apple supplier and iPhone producer in India, was hit by a data breach. As a result, it was reported that more than 200,000 trade secrets and confidential documents belonging to Apple and Tesla were stolen by the ransomware group World Leaks. According to Reuters, the group has now leaked supplier lists, component details, and photos of the upcoming iPhone 18 Pro models on the dark web. One of the materials leaked by the hackers is a drop-test video of the iPhone 18 Pro, which is due to launch this September. The phone is shown in a gray color and has the same familiar design we saw on last year's iPhone 17 Pro series. The device also appears to be quite durable, though it seems to be thicker than last year's model. One possible explanation is that Apple may be using a larger battery in the iPhone 18 Pro series. Moreover, Reuters says it has seen at least six documents mapping many components in the iPhone 18 Pro models to their respective suppliers, including details on chips on the main circuit board and on battery and camera components. The documents reportedly detail hundreds of parts that will be used in the iPhone 18 Pro models. A person familiar with the matter told the outlet that Apple classifies this data as sensitive and “is concerned about the documents being shared on the dark web as they relate to unreleased models.” Apple is reportedly investigating the issue but has yet to issue an official statement.
    • You do you, I've just said that it first appeared in "home" version before it will be available in "work" one. I use Edge only because it still supports MV2 uBO extension even on Android - I'll switch when they stop.
    • I imagine that was a review or something? My reviews mostly contain a lot of images and galleries, but these are all webp too, but yeah it all adds up on the page load. Would help if you were more helpful with your critique instead of bitching and moaning like a Karen 😂 Because then we might be able to fix it for you.
    • If Valve refused to let them make the case, I wonder if they've already partnered with someone else to do it? The fact that they didn't seek permission/licence before diving straight in is incredible though
  • Recent Achievements

    • First Post
      rosiecharles earned a badge
      First Post
    • Reacting Well
      Juan Dela earned a badge
      Reacting Well
    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      273
    3. 3
      PsYcHoKiLLa
      142
    4. 4
      Steven P.
      100
    5. 5
      macoman
      54
  • Tell a friend

    Love Neowin? Tell a friend!