Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

3/5/2013
03:56 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Government Google Data Requests: Scope Unclear

Google has begun disclosing limited information about U.S. government investigations that demand consumer data and, usually, silence from those cooperating.

Google Chromebook Pixel: Visual Tour
Google Chromebook Pixel: Visual Tour
(click image for larger view and for slideshow)
For the first time, Google has begun providing in its periodic Transparency Reports information about the number of National Security Letters it receives.

National Security Letters (NSL) are demands for information, issued to individuals or organizations by U.S. government agencies, primarily through the FBI, engaged in investigations that affect national security. The FBI uses these letters to obtain transactional information about phone calls and email correspondence from service providers, for example.

One of the things that distinguishes NSLs from other investigatory instruments such as subpoenas is that they typically come with a gag order that prohibits the recipient from revealing that a NSL was received.

Some NSLs have been successfully challenged in court, such as one issued to Brewster Kahle, founder of the Internet Archive, in 2007. But the courts have largely upheld the lawfulness of NSLs, which are supported under the Patriot Act.

[ Who says foreign IT workers are smarter? Read H-1B Workers Not Best Or Brightest, Study Says. ]

In order to reveal that it receives NSLs, Google obtained the consent of the U.S. government. "We're thankful to U.S. government officials for working with us to provide greater insight into the use of NSLs," said Richard Salgado, legal director of law enforcement and information security at Google, in a blog post.

However, Google's disclosure is deliberately vague. It is providing a numerical range of NSLs received rather than a specific number.

"This is to address concerns raised by the FBI, Justice Department and other agencies that releasing exact numbers might reveal information about investigations," explained Salgado.

Google says that it received somewhere between 0 and 999 NSLs each year from 2009 through 2012. Through this imprecise range of NSLs, U.S. authorities sought information about 1000 to 1999 user accounts each year except for 2010, when data about 2000 to 2999 accounts was demanded.

According to the U.S. Department of Justice, 24,287 NSLs were issued in 2010, a 64% increase from a year earlier.

Google declined to provide details about its discussions with government officials beyond noting that officials had been helpful in working with the company to allow limited disclosure. "We've been talking for a long time with the FBI and Department of Justice about how we can provide greater transparency, consistent with the law," a company spokesman said in an email. "They were thoughtful and cooperative in helping us achieve our goal of providing greater transparency about NSLs consistent with the law."

Google has been resisting overreaching government demands for information and censorship since 2005, when it fought the Justice Department's effort to obtain user search data. The company stood up against censorship in China and has continued to improve its Transparency Report over the past few years.

Eva Galperin, global policy analyst for the Electronic Frontier Foundation, said in a phone interview that although the EFF is excited that Google is providing NSL information for the first time, "the downside is that the aggregate numbers are so vague, it's really hard to tell if the number NSLs [Google is receiving] is rising or falling."

She added that the EFF continues to be concerned about NSLs because they're handled in such a secretive manner, with a complete lack of transparency and without sufficient checks and balances. "What you can really learn from this data is just how much we don't know about government surveillance," she said.

Galperin observed that although Google's leadership in transparency has inspired at least half a dozen other companies including Twitter and Sonic.Net, "there are still key players who don't even give us the most basic information about government requests." She said those key players include Facebook and Microsoft, which owns Skype.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-0532
PUBLISHED: 2021-06-21
In memory management driver, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-185196177
CVE-2021-0533
PUBLISHED: 2021-06-21
In memory management driver, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-185193932
CVE-2021-26461
PUBLISHED: 2021-06-21
Apache Nuttx Versions prior to 10.1.0 are vulnerable to integer wrap-around in functions malloc, realloc and memalign. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution.
CVE-2021-0478
PUBLISHED: 2021-06-21
In updateDrawable of StatusBarIconView.java, there is a possible permission bypass due to an uncaught exception. This could lead to local escalation of privilege by running foreground services without notifying the user, with User execution privileges needed. User interaction is not needed for explo...
CVE-2021-0504
PUBLISHED: 2021-06-21
In avrc_pars_browse_rsp of avrc_pars_ct.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure over Bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: ...