Two U.S. Congressmen have called on the Department of Justice to reopen its investigation into Google, after revelations that the company's Street View vehicles recorded large amounts of unencrypted Wi-Fi data. Although Google had maintained that the data collection was accidental, last month a new report revealed that the data collection was, in fact, by design.

"In light of this, we are writing to request that the Department [of Justice] evaluate ... whether it would be appropriate to re-open its investigation to assess whether Google's conduct may in fact have violated the law," wrote Frank Pallone Jr. (D-NJ) and John Barrow (D-Ga.) Thursday in a letter to Attorney General Eric Holder. "By ensuring that this matter is investigated to the fullest extent, we can understand what happened and how it can be prevented from ever happening again."

Google has long maintained that although the data collection might have been inappropriate, it wasn't illegal. "We have always been clear that the leaders of this project did not want or intend to use this payload data. Indeed Google never used it in any of our products or services," a Google spokesman said via email. "Both the DoJ and the FCC have looked into this closely--including reviewing the internal correspondence--and both found no violation of law."

The Federal Trade Commission in October 2010 also declined to fine Google following its Street View investigation, although the FTC received assurances from Google that it would delete all inadvertently collected Wi-Fi payload data. Google also said that it had already put new business processes in place to help prevent similar incidents from reoccurring. In May 2011, meanwhile, the Department of Justice declined to prosecute Google after investigating whether the company had violated the Wiretap Act.

Last month, however, the FCC released a report that included testimony from Google employees who had direct knowledge of the Street View program. Although Google had long maintained--and executives might have believed--that the Wi-Fi data collection was accidental, the report disclosed that "the data collection resulted from a deliberate software design decision by one of the Google employees working on the Street View project," and was detailed in a design document approved by managers.

In other words, Google actively engaged in wardriving, which is the practice of driving around and looking for accessible wireless networks or wireless data traffic, then sniffing and storing the data they're sending and receiving. But it's not clear whether this practice would have violated any U.S. laws.

In the wake of the report, European investigators are reportedly considering reopening their Google Street View investigations. Notably, although Canada and multiple European countries found that Google had violated their privacy laws, they let the matter rest after Google agreed to delete collected data and revise its privacy practices. France, meanwhile, also hit Google with a record privacy fine.

The FCC also fined Google $25,000 for having obstructed its investigation, but not for violating communications, wiretapping, or any other U.S. laws or regulations. Still, according to the FCC's report, "significant factual questions" remained unanswered, owing to the engineer who added the war-driving capabilities to Street View having "invoked his Fifth Amendment right against self-incrimination and declined to testify."

Might Google be called on to now answer those factual questions?

Mobile Connect addresses the strategic direction that will define enterprise IT for the next decade--building and managing information systems that run on a mobile platform. Mobile Connect will bring together enterprise mobility thought leaders to discuss the innovations in mobile, and how forward-thinking companies are getting the technology to work for them, providing unprecedented business value. It happens in Boston, June 18-20. Register today.

Hey Congress, are you just wanna be Europeans. How about supporting American companies instead of jumping on the bandwagon. This is another one for the "If I wanted to destroy America" series. If you can't work out a backroom deal with an American corporation, then you don't deserve to be in office. And, oh yeah Pallone, I live in N.J. Want to bet which way I'll be voting the next time you run for office? I think all elected officials should be under constant investigation because when the spot light is focused, many of them are revealed as self-serving hypocrites if not criminals.

"unencrypted Wi-Fi data" Say it with me "UN EN CRYPTED WI FI DATA". Doesn't the DOJ have more important things to do like go after online poker players? Congress has MUCH more important issues to deal with, as does the DOJ. If networks choose (or are too stupid not to) run their nets PUBLICLY - then so be it - the info is available to ANYONE that cares to let their computer connect to random networks.

"If you can't work out a backroom deal" sounds like the standard methods used in Greece, Italy, and a few other mediterranean bordering countries. Is their economic state of affairs what you would propose we use as a model of excellence? The point is not the unencrypted data as much as it is the active harvesting of that information and undisclosed use. Until next to the WiFi enabled signs there is a disclosure that reminds people they are using unsecured networks, I'm assuming that most individuals are not aware/uninformed which is separate and distinct from the majority which read and post comments to InformationWeek articles.

Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.

Published: 2017-05-09NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

Published: 2017-05-08unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

Published: 2017-05-08Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

Published: 2017-05-08Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.