Language Selection

English French German Italian Portuguese Spanish

FBI wants more subpoena power

Filed under
Security

FBI Director Robert Mueller said Wednesday that Congress should give the agency the power to issue its own subpoenas, instead of having to get approval for them from a court, so that it can collect information more quickly in terrorism investigations.

Mueller said North Carolina State University initially rebuffed FBI investigators this month when they sought enrollment records for a former graduate student suspected of being linked to the London bombings because the investigators did not have a subpoena.

Although the FBI eventually obtained subpoenas and the records, Mueller used the episode to argue to the Senate Judiciary Committee that the bureau needs the new subpoena power.

"We should've been able to have a document, an administrative subpoena, that we took to the university and got those records immediately," Mueller told the committee.

Lawmakers are trying to determine whether to include FBI subpoena power for gathering anti-terror intelligence in a package of amendments to the USA Patriot Act.

Mueller said he objects to any oversight of an FBI subpoena outside of the bureau.

But Sen. Dianne Feinstein (D-Calif.) said she is leery of giving the FBI anti-terror subpoena power without some Justice Department supervision. The FBI already has the authority to issue administrative subpoenas in certain kinds of cases.

Feinstein said an agent seeking to issue a subpoena should be required to justify the need for it to an assistant U.S. attorney because of the possibility that the FBI would amass information about innocent people.

"The resistance to this makes me suspicious," she said.

At North Carolina State, the FBI sought records for Magdy el-Nashar, an Egyptian who attended the university in 2000 and was believed to have rented a house in Leeds, England, near where four bombs used in the July 7 attacks in London are thought to have been made. The attacks killed 56 people.

El-Nashar, who is wanted for questioning by British authorities, has been detained in Egypt. Officials there have said he has no links to the bombings.

In a statement, the university said that under federal privacy laws, it could not turn over records without a subpoena. In all, North Carolina State eventually was served with three subpoenas pertaining to el-Nashar, the statement said.

Mueller's visit to Capitol Hill coincided with the release of a report by Justice Department Inspector General Glenn Fine that found continued shortcomings in FBI efforts to translate a backlog of foreign-language material, including information related to counterterrorism.

The report found that the FBI now has 8,354 hours of tape recordings involving counterterrorism topics waiting to be reviewed, up from 4,086 hours a year ago. But Fine found that the bureau is up-to-date in translating material deemed "highest priority," a category that includes information relating to Al Qaeda terrorism cases.

On another sore subject for the agency, Mueller said the FBI has made "substantial progress" in upgrading its much maligned technology systems. He said the bureau has bought more powerful computers and built a new secure network.

A contractor for a new case management system, code-named Sentinel, is expected to be selected by the end of the year, he said. Sentinel is slated to be implemented in four stages over 40 months, ending in 2009.

An earlier attempt at a case management systemwas scrapped after three years and an expenditure of $170 million.

By Andrew Zajac
Washington Bureau

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers