Endpoint //

Privacy

8/13/2014
04:30 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

NSA Collected More Records Than Court Allowed

New documents show the Foreign Intelligence Surveillance Court is stumped by the NSA's "systemic overcollection."

The Electronic Privacy Information Center (EPIC) has obtained documents that show that the National Security Agency consistently violated some of the restrictions the Foreign Intelligence Surveillance Court (FISC) placed upon the NSA's Internet Metadata program.

Despite all the redactions, the documents make it evident that compliance officials did not provide adequate oversight, and that the NSA collected more information than it was authorized to collect, widely shared information with agents and agencies not authorized to view it, and tried to persuade the court to act outside its own authority and grant wider permissions than legislation would allow.

The details about what precisely was approved by the FISC are mostly redacted. Whatever they are, the NSA acquired more "categories of information" than it was permitted to acquire. However, the court seems to waver in its assessment of whether the NSA officials were just ignorant or willfully playing dumb.

From the documents:

    As described by the government, the unauthorized collection resulted from failures to [REDACTED] in the manner required... By the government's account, the lack of required [REDACTED] did not result from technical difficulty or malfunction, but rather from a failure of "those NSA officials who understood in detail the requirements"... The government assessed the violations to have been caused by "poor management, lack of involvement by compliance officials, and lack of internal verification procedures -- not by bad faith."

No matter the reason, the NSA committed what the court called "systemic overcollection" for years. Nearly every stored record included at least one piece of data the agency was not authorized to keep.

    The government has said nothing about how the systemic overcollection was permitted to continue... On the record before the Court, the most charitable interpretation possible is that the same factors identified by the government [REDACTED] remained unabated in full effect: non-communication with the technical personnel directly responsible [REDACTED] resulting from poor management. However, given the duration of this problem, the oversight measures ostensibly taken since [REDACTED] to detect overcollection, and the extraordinary fact that NSA's end-to-end review overlooked unauthorized acquisitions that were documented in virtually every record of what was acquired, it must be added that those responsible for conducting oversight at NSA failed to do so effectively.

The documents further state:

    The Court had specifically directed the government to explain whether this unauthorized collection involved the acquisition of information other than the approved Categories... In response, the Deputy Secretary of Defense stated that the "Director of NSA has informed me that at no time did NSA collect any category of information... other than the [REDACTED] categories of meta data" approved... This assurance turned out to be untrue.

    Regarding the information obtained through unauthorized collection, the Court ordered the government to describe whether it "has been, or can be, segregated from information that NSA was authorized to collect," "how the government proposes to dispose of" it, and "how the government proposes to ensure that [it] is not included ... in applications presented to this Court."

Upon review, the NSA decided that the collected data could not be sufficiently segregated. It simply "eliminated access to the database" altogether.

However, the NSA still wanted to access and use some of the records it had collected without authorization, asserting that the records were important to national security. The FISC was ultimately swayed by the government's assertions and therefore granted, "albeit reluctantly," the right to access, use, and disseminate the "overcollected" information.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
8/18/2014 | 4:30:12 PM
Re: what's new?
The TAO unit made an error, their intent was to implant a malware in the Syrian system to hijack the traffic and spy on their Government.

The incident represented a serious risk for US 

 
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
8/18/2014 | 4:03:15 PM
Re: what's new?
Hey Pierluigi! Thanks for sharing that link. Interesting that the headline says NSA "accidently" caused the Syrian Internet blackout. I'm not sure whether it's scarier if they did it on purpose or by mistake. 

 

 

securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
8/14/2014 | 11:52:00 AM
Re: what's new?
Hi Marylin ... have you read about the Intenet Blackout in Syria 2012 ... 

 

http://securityaffairs.co/wordpress/27568/intelligence/internet-blackout-syria-nsa.html

 

NSA seems to be everywhere ;-)
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
8/14/2014 | 11:19:59 AM
Re: what's new?
I'm not surprised either. Nor am I confident that the FISC has the technological expertise to  make the proper judgements in these matters.
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
8/13/2014 | 5:27:10 PM
what's new?
I'm not surprised ... what we know it is just the tip of the iceberg ... and don't forget that NSA isn't unique intelligence that use technology to monitor communications and Internet access worldwide.

I'm not surprised ....
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-18913
PUBLISHED: 2019-03-21
Opera before 57.0.3098.106 is vulnerable to a DLL Search Order hijacking attack where an attacker can send a ZIP archive composed of an HTML page along with a malicious DLL to the target. Once the document is opened, it may allow the attacker to take full control of the system from any location with...
CVE-2018-20031
PUBLISHED: 2019-03-21
A Denial of Service vulnerability related to preemptive item deletion in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor ...
CVE-2018-20032
PUBLISHED: 2019-03-21
A Denial of Service vulnerability related to message decoding in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor daemon t...
CVE-2018-20034
PUBLISHED: 2019-03-21
A Denial of Service vulnerability related to adding an item to a list in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor ...
CVE-2019-3855
PUBLISHED: 2019-03-21
An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.