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
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19551
PUBLISHED: 2019-12-06
In userman 13.0.76.43 through 15.0.20 in Sangoma FreePBX, XSS exists in the User Management screen of the Administrator web site. An attacker with access to the User Control Panel application can submit malicious values in some of the time/date formatting and time-zone fields. These fields are not b...
CVE-2019-19552
PUBLISHED: 2019-12-06
In userman 13.0.76.43 through 15.0.20 in Sangoma FreePBX, XSS exists in the user management screen of the Administrator web site, i.e., the/admin/config.php?display=userman URI. An attacker with sufficient privileges can edit the Display Name of a user and embed malicious XSS code. When another user...
CVE-2019-19620
PUBLISHED: 2019-12-06
In SecureWorks Red Cloak Windows Agent before 2.0.7.9, a local user can bypass the generation of telemetry alerts by removing NT AUTHORITY\SYSTEM permissions from a malicious file.
CVE-2019-19625
PUBLISHED: 2019-12-06
SROS 2 0.8.1 (which provides the tools that generate and distribute keys for Robot Operating System 2 and uses the underlying security plugins of DDS from ROS 2) leaks node information due to a leaky default configuration as indicated in the policy/defaults/dds/governance.xml document.
CVE-2019-19627
PUBLISHED: 2019-12-06
SROS 2 0.8.1 (after CVE-2019-19625 is mitigated) leaks ROS 2 node-related information regardless of the rtps_protection_kind configuration. (SROS2 provides the tools to generate and distribute keys for Robot Operating System 2 and uses the underlying security plugins of DDS from ROS 2.)