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.

IoT
3/18/2019
05:45 PM
50%
50%

New IoT Security Bill: Third Time's the Charm?

The latest bill to set security standards for connected devices sold to the US government has fewer requirements, instead leaving recommendations to the National Institute of Standards and Technology.

For the third time in as many years, lawmakers have introduced a bill that would require Internet of Things (IoT) products sold by federal contractors and vendors to abide by government guidelines to ensure a baseline of cybersecurity.

The current bill, supported by members of both parties and known as the Internet of Things Cybersecurity Improvement Act of 2019, eschews specific recommendations and instead calls for the National Institute of Standards and Technology (NIST) to develop security guidelines for IoT devices sold to the US government. 

The hope is that such legislation, if signed into law, would mean more secure IoT equipment overall, including in the consumer and commercial sector.

It is the latest attempt to convince manufacturers of connected devices to take security more seriously. The original legislation, known as the Internet of Things Cybersecurity Improvement Act of 2017, was introduced after the Mirai botnet targeted Internet infrastructure provider Dyn and disrupted a wide variety of other Internet services in October 2016. Mirai compromised weakly secured digital video recorders and connected cameras, creating a botnet of more than 100,000 endpoints that leveled a series of distriubted denial-of-service (DDoS) attacks on Dyn

The original bipartisan IoT security legislation required that any device sold to the US government followed basic, well-established cybersecurity norms, such as no hard-coded passwords and being easily patchable. Even so, the legislation failed to overcome industry resistance.

The new IoT security legislation will likely result in the same requirements, because the original bill had only focused on common-sense, or "evergreen," guidelines, says Josh Corman, chief security officer for PTC, a maker of industrial IoT solutions.

"I think we are going to end up in a similar place, but later," he says. "So it means more exposure to threats and less secure devices being brought to market."

The bill is all about using the government's buying power as an incentive for companies to create more secure connected devices, Sen. John Warner, D-Va., vice chairman of the Senate Select Committee on Intelligence and a co-sponsor of the bill, said in a statement.

"While I'm excited about their life-changing potential, I'm also concerned that many IoT devices are being sold without appropriate safeguards and protections in place, with the device market prioritizing convenience and price over security," he said.

The current bill tasks NIST with creating requirements for federal agencies that consider the secure development, identity management, patching and configuration management of IoT devices. In addition, NIST is also tasked with developing recommendations on the management and use of IoT devices by March 31, 2020.

By removing the exact requirements from the legislation, lawmakers have eased the way to passage, says Nathan Owens, an attorney and partner with the law firm of Newmeyer & Dillion, who focuses on risk management and cybersecurity.

For lawmakers under pressure from the industry, "making it broader and going to an organization like NIST is easy to get behind," he says. "It makes the (passage of the) legislation really easy and palatable."

Within six months of the passage of the bill, NIST will be required to issue a report on the impact connected devices will have on federal operations and how agencies can mitigate cybersecurity risk. In addition, the bill specifically calls for NIST to develop coordinated vulnerability disclosure guidelines.

Finally, the bill would require the Office of Management and Budget to issue guidelines for each federal agency, following the NIST report and creation of recommendations with regards to internet-of-things technology. The bill requires that all federal contractors and vendors adhere to these guidelines.

Feds Only

While legislators aim to broadly impact the security of IoT devices through the power of federal purchasing, the bill itself only focuses on government requirements for the devices that agencies buy for their own use, says PTC's Corman. If the Pentagon purchases battlefield systems, they want to make sure that they cannot be hacked by other nations' militaries.

"The government has every right as a purchaser of device to want to have those products not be hackable or trackable," he says. "The manufacturers of a $100 device don't realize that, if its deployed by the federal government, that the attack surface and threat model is markedly different."

In many ways the legislation already follows the precedent set in legislation passed by California late last year, which requires manufacturers to incorporate "reasonable security feature or features" into IoT devices.

In a May 2018 report on defending against botnets and automated threats, the US Department of Homeland Security and US Department of Commerce recommended that technology and products include security at every stage of their development and manufacture. In addition, the report argued that the federal government should use its purchasing power to incentivize manufacturers to create more secure technology.

"Product developers, manufacturers, and vendors are motivated to minimize cost and time to market, rather than to build in security or offer efficient security updates," the report stated. "Market incentives must be realigned to promote a better balance between security and convenience when developing products.

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
How to Think Like a Hacker
Dr. Giovanni Vigna, Chief Technology Officer at Lastline,  10/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4031
PUBLISHED: 2019-10-16
IBM Workload Scheduler Distributed 9.2, 9.3, 9.4, and 9.5 contains a vulnerability that could allow a local user to write files as root in the file system, which could allow the attacker to gain root privileges. IBM X-Force ID: 155997.
CVE-2019-17626
PUBLISHED: 2019-10-16
ReportLab through 3.5.26 allows remote code execution because of toColor(eval(arg)) in colors.py, as demonstrated by a crafted XML document with '<span color="' followed by arbitrary Python code.
CVE-2019-17627
PUBLISHED: 2019-10-16
The Yale Bluetooth Key application for mobile devices allows unauthorized unlock actions by sniffing Bluetooth Low Energy (BLE) traffic during one authorized unlock action, and then calculating the authentication key via simple computations on the hex digits of a valid authentication request. This a...
CVE-2019-17625
PUBLISHED: 2019-10-16
There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such...
CVE-2019-17624
PUBLISHED: 2019-10-16
In X.Org X Server 1.20.4, there is a stack-based buffer overflow in the function XQueryKeymap. For example, by sending ct.c_char 1000 times, an attacker can cause a denial of service (application crash) or possibly have unspecified other impact.