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

8/13/2019
02:00 PM
Connect Directly
LinkedIn
RSS
E-Mail vvv
50%
50%

The California Consumer Privacy Act's Hidden Surprise Has Big Legal Consequences

The CCPA's provision devoted to 'reasonable' cybersecurity procedures and policies could trip up your business. Get ready now.

In 2018, when businesses were preparing for the European Union's General Data Privacy Regulation (GDPR), California quietly and quickly passed its own legislation: the California Consumer Privacy Act (CCPA). This regulation, with its emphasis on consumer privacy rights, has an interesting history of grassroots consumer advocacy coupled with swift legislative action provoked by the fear of a ballot initiative. But what security professionals may have missed is that the CCPA contains a surprise in the form of a provision devoted to "reasonable" cybersecurity procedures and policies.

Many businesses hope that the CCPA will change — serious amendments remain in the California legislative pipeline and should hit the governor's desk this fall. However, the meat of the CCPA will likely remain the same. Now is the time to start preparing, especially for the cybersecurity standards, as the regulation goes into effect on January 1, 2020, with enforcements starting July 1, 2020.

Who Is Affected?
Not every business is covered by the CCPA; instead, it defines affected businesses in this way:

  • Businesses with annual gross revenues in excess of $25 million dollars
  • Those that purchase, sell, or share data from more than 50,000 consumers, households, or devices
  • Those that derive 50% or more of their annual revenue from selling consumers' personal information

There is no physical requirement for businesses to be based in California. If your business interacts with California residents — even through a website — and has gross revenues in excess of $25 million, you should start preparing for the CCPA.

The Hidden Security "Duty" in the Private Cause of Action
Tucked into the CCPA's provision on consumers having a private right of action to sue businesses when their "nonencrypted or nonredacted personal information" is subjected to "unauthorized access, theft, or disclosure" is the security requirement. The CCPA specifies that people can sue "as a result of the business' violation of the duty to implement and maintain reasonable security procedures and practices appropriate to the nature of the information." This is, in effect, a regulatory mic drop. Suddenly, baked into the CCPA is a business's "duty" to maintain "reasonable security procedures and practices" appropriate to the sliding scale of the sensitivity of the information. Unfortunately, those reasonable security procedures and practices are left undefined in the CCPA itself.

The CCPA now specifies penalties of $100 to $750 per incident per consumer plus actual damages plus injunctive relief. However, now a judge may consider a defendant's "assets, liabilities, and net worth" in determining the damages.

Defining Duty and Reasonable Measures from Earlier California Laws
Arguably, under California common law (made by cases rather than by statutes), the duties articulated in the CCPA already existed. In 2016, the Office of the Attorney General in California published a document called the "Data Breach Report."  The Attorney General’s Data Breach Report articulated reasonable security practices, citing the Center for Internet Security's 20 security controls as the baseline for an information security program.

Without additional guidance from the California legislature or Attorney General, businesses will need to build reasonable security measures from additional sources, including the National Institute of Standards and Technology’

But that's not enough; the CCPA also states that a business must have various policies in place as well. The Act remains silent as to what policies beyond specific mentions of updating privacy policies, but it is clear that the Act also intends that businesses dust off ancient incident response plans, bring your own device policies, and various other security policies to make certain they are up to date.

What to Do Now
Reach out for help. Start by consulting with a lawyer to create a compliance plan of attack based on your business needs. This doesn't need to be expensive, but it's time to pick up the phone and ask questions. Many businesses took data inventories to comply with GDPR and now it's time to begin that process again, searching out California resident data. Specifically, this summer you should look hard at your security program to see if it would be considered reasonable to a California judge and jury. If the answer is no, use the CCPA as the impetus to begin in earnest the changes necessary to bring your business into compliance.

Related Content:

Beth Burgin Waller is a lawyer who knows how to navigate between the server room and the board room. As chair of the cybersecurity & data privacy practice at Woods Rogers, she advises clients on cybersecurity and on data privacy concerns. In this capacity, she ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Zero Trust doesn't have to break your budget!
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34202
PUBLISHED: 2021-06-16
There are multiple out-of-bounds vulnerabilities in some processes of D-Link AC2600(DIR-2640) 1.01B04. Ordinary permissions can be elevated to administrator permissions, resulting in local arbitrary code execution. An attacker can combine other vulnerabilities to further achieve the purpose of remot...
CVE-2021-32659
PUBLISHED: 2021-06-16
Matrix-appservice-bridge is the bridging service for the Matrix communication program's application services. In versions 2.6.0 and earlier, if a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombs...
CVE-2020-25755
PUBLISHED: 2021-06-16
An issue was discovered on Enphase Envoy R3.x and D4.x (and other current) devices. The upgrade_start function in /installer/upgrade_start allows remote authenticated users to execute arbitrary commands via the force parameter.
CVE-2020-25754
PUBLISHED: 2021-06-16
An issue was discovered on Enphase Envoy R3.x and D4.x devices. There is a custom PAM module for user authentication that circumvents traditional user authentication. This module uses a password derived from the MD5 hash of the username and serial number. The serial number can be retrieved by an una...
CVE-2020-25753
PUBLISHED: 2021-06-16
An issue was discovered on Enphase Envoy R3.x and D4.x devices with v3 software. The default admin password is set to the last 6 digits of the serial number. The serial number can be retrieved by an unauthenticated user at /info.xml.