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
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7245
PUBLISHED: 2020-01-23
Incorrect username validation in the registration processes of CTFd through 2.2.2 allows a remote attacker to take over an arbitrary account after initiating a password reset. This is related to register() and reset_password() in auth.py. To exploit the vulnerability, one must register with a userna...
CVE-2019-14885
PUBLISHED: 2020-01-23
A flaw was found in the JBoss EAP Vault system in all versions before 7.2.6.GA. Confidential information of the system property's security attribute value is revealed in the JBoss EAP log file when executing a JBoss CLI 'reload' command. This flaw can lead to the exposure of confidential information...
CVE-2019-17570
PUBLISHED: 2020-01-23
An untrusted deserialization was found in the org.apache.xmlrpc.parser.XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code. Apache XML-RPC is no longer maintained and this issue...
CVE-2020-6007
PUBLISHED: 2020-01-23
Philips Hue Bridge model 2.X prior to and including version 1935144020 contains a Heap-based Buffer Overflow when handling a long ZCL string during the commissioning phase, resulting in a remote code execution.
CVE-2012-4606
PUBLISHED: 2020-01-23
Citrix XenServer 4.1, 6.0, 5.6 SP2, 5.6 Feature Pack 1, 5.6 Common Criteria, 5.6, 5.5, 5.0, and 5.0 Update 3 contains a Local Privilege Escalation Vulnerability which could allow local users with access to a guest operating system to gain elevated privileges.