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.

Endpoint //

Privacy

10/16/2014
05:45 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

FBI Director Urges New Encryption Legislation

Encryption algorithms do not acknowledge "lawful access."

Though encryption is one of the strongest tools in the data security and privacy compliance toolkit, unchecked encryption could "lead us all to a very, very dark place," in which murderers, child abusers, and other criminals walk free, according to FBI Director James Comey.

"The place that this is leading us is one that I would suggest we shouldn't go without careful thought and public debate," Comey said at an event at the Brookings Institute in Washington.

He was responding to new moves by Apple and Google to expand encryption capabilities on iOS and Android devices. Google has announced it will provide data encryption by default in its next version of Android. Apple recently added two-factor authentication to iCloud and has created new encryption offerings on iOS 8 that give the encryption keys to the customer -- the idea being that, if Apple does not retain the keys, it cannot decrypt customers' data, even if the government demands it.

These measures are cloud services' and mobile device companies' way of regaining the trust of customers concerned about the US government's history of subpoenaing these companies for access to individuals' communications and private data.

[Read about new "encryption-in-use" technologies that keep keys in the hands of consumers, not cloud companies.]

Consumers and privacy advocates applaud those efforts, but Comey cautioned that they could come at a terrible price.

"If this becomes the norm, I suggest to you that homicide cases could be stalled, suspects walked free, child exploitation not discovered and prosecuted," he said. "Law enforcement needs to be able to access communications in a lawful way in order to bring people to justice. Those charged with protecting our people aren't able to access the evidence we need, even with lawful authority."

Though they may obtain the legal authority to intercept communications and access other information with court orders, he said, they often lack the technical ability to crack open that data once they have it. "Unfortunately, the law hasn't kept pace with technology, and this disconnect has created a significant public safety problem."

Comey suggested that the Communications Assistance for Law Enforcement Act, enacted in 1994, is due for an update. CALEA was created because of the FBI's concern that use of digital telephone exchange switches would obstruct intelligence agencies' ability to tap phones. The act required telecoms and telecom equipment suppliers to build in surveillance capabilities so that the government could actually conduct wiretaps if they first obtained lawful authority to do so. The act was expanded over the years to cover VoIP and broadband Internet, as well, but Comey suggested that the act must be updated again with high-level encryption in mind.

"We are not seeking a backdoor approach," he said. "We are completely comfortable with court orders and lawful authority. With sophisticated encryption, there may be no solution at all, leaving us at a dead end."

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
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
10/21/2014 | 11:37:51 AM
Re: Tradeoff
Totally agree that law enforcement officials like FBI Director James Comey have a long way to go to reassure the public that they are not overreaching in the name of pubic security.  But getting out in front of public policy institutions like Brookings, is at least a small step in the right direction...
Robert McDougal
100%
0%
Robert McDougal,
User Rank: Ninja
10/17/2014 | 11:25:45 AM
Re: Tradeoff
"Law enforcement needs to be able to access communications in a lawful way in order to bring people to justice."

I'm very sorry but you (the government) didn't seem to be content with accessing communications in a 'lawful way' not too long ago, why would I trust you now?
RobertM866
100%
0%
RobertM866,
User Rank: Apprentice
10/17/2014 | 8:39:07 AM
Re: Tradeoff
Not when any such discussion will invariably lead to a lessening of protections against government spying and interference into the public's private affairs.  

The old saying was, the most frightening words one could here were "I'm from the government, and i'm here to help".  I would argue that more frightening is "in the name of public safety" or "national secuirty". 
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
10/17/2014 | 8:24:17 AM
Re: Tradeoff
"We are completely comfortable with court orders and lawful authority. "

Except when government agencies break the rules in the name of public safety. That said,  it's hard to argue against a full-throated debate about encryption and how to update existing laws. Is Congress up to the task? <sigh>
Joe Stanganelli
100%
0%
Joe Stanganelli,
User Rank: Ninja
10/17/2014 | 7:43:07 AM
Tradeoff
As Benjamin Franklin wrote: "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."

And besides, when people are like, "Thanks, government, but I'll take my chances with the murderers," you know that government has a huge credibility problem.
Major Brazilian Bank Tests Homomorphic Encryption on Financial Data
Kelly Sheridan, Staff Editor, Dark Reading,  1/10/2020
Exploits Released for As-Yet Unpatched Critical Citrix Flaw
Jai Vijayan, Contributing Writer,  1/13/2020
Microsoft Patches Windows Vuln Discovered by the NSA
Kelly Sheridan, Staff Editor, Dark Reading,  1/14/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Give us your best shot! You might win an Amazon gift card!
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
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-2019-3686
PUBLISHED: 2020-01-17
openQA before commit c172e8883d8f32fced5e02f9b6faaacc913df27b was vulnerable to XSS in the distri and version parameter. This was reported through the bug bounty program of Offensive Security
CVE-2019-3683
PUBLISHED: 2020-01-17
The keystone-json-assignment package in SUSE Openstack Cloud 8 before commit d7888c75505465490250c00cc0ef4bb1af662f9f every user listed in the /etc/keystone/user-project-map.json was assigned full &quot;member&quot; role access to every project. This allowed these users to access, modify, create and...
CVE-2019-3682
PUBLISHED: 2020-01-17
The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node.
CVE-2019-17361
PUBLISHED: 2020-01-17
In SaltStack Salt through 2019.2.0, the salt-api NEST API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.
CVE-2019-19142
PUBLISHED: 2020-01-17
Intelbras WRN240 devices do not require authentication to replace the firmware via a POST request to the incoming/Firmware.cfg URI.