1. Home
  2. |Insights
  3. |Oregon Latest State to Require Reasonable Security for IoT Devices

Oregon Latest State to Require Reasonable Security for IoT Devices

Client Alert | 2 min read | 06.07.19

On May 30, 2019, Oregon became the most recent state to mandate basic security on internet-connected devices with Governor Kate Brown’s signature on H.B. 2395. Oregon’s new statute follows the model of several other states that have introduced or enacted laws requiring security for internet-connected devices. Similar to a California law passed in September 2018, Oregon’s law requires manufacturers of “connected devices” to equip such devices with “reasonable security features.” California and Oregon’s laws will both go into force on January 1, 2020.

Oregon’s law largely tracks California’s 2018 statute, though one key difference appears in its definition of “connected device.” Oregon limits the definition of “connected device” to “any device or physical object that connects directly or indirectly to the Internet and is used primarily for personal, family or household purposes.” In contrast, California’s law applies more broadly to “any device, or other physical object that is capable of connecting to the Internet, directly or indirectly, and that is assigned an Internet Protocol or Bluetooth address.”

Also notable is where Oregon followed California’s lead. Both laws describe “reasonable security features” as methods to protect a connected device that are “appropriate to the nature and function of the device” and the “information it may collect, contain or transmit” – despite criticisms that the definition is fraught with equal parts flexibility and uncertainty. Both also explicitly identify the following mechanisms for authentication from outside a local area network as “reasonable security features”:

  1. A preprogrammed password that is unique for each connected device; or
  2. A requirement that a user generate a new means of authentication before gaining access to the connected device for the first time.
  3. Like California, Oregon generally carves out any security requirements imposed on connected devices by federal law or regulation, and separately explicitly exempt entities or persons that are subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA).

  4. Other state legislatures currently considering similar security requirements for connected devices include Illinois (H.B. 3391), Maryland (S. 553/H.B. 1276), and New York (S.3975/A.B. 2229).

Contacts

Insights

Client Alert | 6 min read | 11.21.26

New Executive Order: “Protecting the Executive’s Privileges and Enhancing Efficiencies in Federal Contracting”

On November 20, President Trump issued “Protecting the Executive’s Privileges and Enhancing Efficiencies in Federal Contracting,” directing all federal contractors to “immediately” notify the White House and contracting agencies of pending or future congressional requests concerning their communications or work with the executive branch. According to the executive order (EO), contractors must also follow instructions to withhold communications from Congress that the White House or contracting agency determines are protected by executive privilege. The order also reaches subcontractors working on federal contracts. Agencies are directed to coordinate appropriate responses and privilege assertions, including by making primes responsible for ensuring subcontractor compliance....