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/Embedded Security

9/19/2018
08:05 AM
Joe Stanganelli
Joe Stanganelli
Joe Stanganelli
50%
50%

California Looks to Pass Rudimentary IoT Security Legislation

A California bill specific to IoT cybersecurity measures sits on Gov. Jerry Brown's desk, ready for him to sign it into law. The wording and limits of the law, however, leaves questions as to just how big an effect it will have.

A recently passed California bill may begin to set a legislative standard in the US for basic Internet of Things (IoT) security, but it's such a low and vague standard in such a politically unfashionable area that it may not signal much in terms of what's to come.

Earlier this month, the California state legislature presented legislation on minimum IoT-security requirements to Gov. Jerry Brown for signature. If Brown signs the bill into law, it will go into effect on January 1, 2020.

The legislation dictates that device manufacturers equip devices with "a reasonable security feature or features" against attacks and compromises. It also specifies that such feature(s) must be "appropriate" for both the device itself -- taking into account its functionality -- and the type of information the device handles.

IoT-regulation skeptics have long complained that one big problem of IoT-related laws and regulations is that there can be no practical one-size-fits-all; by definition, an IoT device can literally be just about anything.

Getting something done
The device-appropriate requirement makes compliance less of a headache for manufacturers because it is almost a non-requirement. While it's clear that the bill requires devices to feature at least somethingin the way of meaningful and relevant security, it is hard to imagine a manufacturer going to the trouble to make and market a device with security features so inappropriately complex or burdensome as to make the device unusable -- or a regulatory agency initiating action in such a case.

The coinciding requirement of information appropriateness may give the law some juice, however -- potentially more stringently impacting devices that deal with more sensitive information. A smart washer-dryer set probably wouldn't need nearly as strong security for compliance as, say, an Amazon Echo acting as an automation hub that listens to and records every word it "hears" would.

Still, the bill's requirements are vague (particularly because of that fluffy word "reasonable," which tends to set a very low bar in legal contexts) and it offers manufacturers numerous exceptions and outs.

Perhaps the only real meat in the California bill lies in what it has to say on the reasonableness of default authentication setups.

It clarifies that manufacturers of devices "equipped with a means for authentication outside a local area network" automatically satisfy the reasonableness requirement by either (1) preprogramming unique passwords to each respective device or (2) installing a feature that does not grant initial access until the user "generate[s] a new means of authentication."

The bill continues that such a feature must still meet the appropriateness requirements while being "[d]esigned to protect the device and any information contained therein from unauthorized access, destruction, use, modification, or disclosure." This caveat appears superfluous, however. Standard implementations of (1) unique default passwords and (2) forced user-generated authentication on first use, respectively, are features that are almost certainly so appropriate and so designed.

By specifically identifying either of these two features as a means of effective compliance for Internet- or Bluetooth-connected devices, while being vague on just about everything else, the legislation acts as a strong suggestion to manufacturers to stop shipping devices with non-unique passwords -- or no authentication measure at all. At the same time, it permissively bows to industry interests if manufacturers decide that they have a better idea.

Fed fail
Even with all this vagueness and permissibility, and even considering it effectively took over a year and a half from its February 2017 introduction to finalize and jointly pass this legislation in both the state senate and the state assembly, to do that much as a legislature on IoT security is a relatively boastworthy victory for politicians when compared to such efforts at the federal level.

Numerous attempts at federal IoT-security legislation over the past couple of years have died in committee.

Cybersecurity pundits call the present bill the first IoT-specific legislation in the US, but that honor has already been taken; this bill is not even the first IoT-specific law in California.

In 2015, after a consumer-data scandal surrounding smart-television manufacturer Vizio, Calif. enacted a law putting strict requirements on the implementation of voice-recognition technology and limitations on the use of voice-recognition data by smart-television manufacturers and others. In 2006, California passed a law imposing similar, stricter requirements and limitations upon satellite and cable companies regarding monitoring, collecting and using subscriber data.

It seems, California has been leading the nation on IoT-security statutes for some time; it remains uncertain as to when -- or if -- other US lawmakers will follow.

Related posts:

—Joe Stanganelli, principal of Beacon Hill Law, is a Boston-based attorney, corporate-communications and data-privacy consultant, writer, and speaker. Follow him on Twitter at @JoeStanganelli.

(Disclaimer: This article is provided for informational, educational and/or entertainment purposes only. Neither this nor other articles here constitute legal advice or the creation, implication or confirmation of an attorney-client relationship. For actual legal advice, personally consult with an attorney licensed to practice in your jurisdiction.)

 

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/2/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9498
PUBLISHED: 2020-07-02
Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
CVE-2020-3282
PUBLISHED: 2020-07-02
A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
CVE-2020-5909
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
CVE-2020-5910
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
CVE-2020-5911
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.