Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

What Does the CCPA Cybersecurity Audit Assess for Business Continuity and Disaster Recovery (§ 7123(c)(18))?

Short Answer

CCPA regulation § 7123(c)(18) requires the cybersecurity audit to assess, if applicable, business continuity and disaster recovery plans, including data recovery capabilities and backups. This supports the § 7123(a) goal of protecting against unauthorized activity that results in loss of availability of personal information.

CCPA § 7123(c)(18) at a Glance

  • Regulation: California Consumer Privacy Act (CCPA) regulations, California Code of Regulations, Title 11, Division 6, Chapter 1, Article 9 (Cybersecurity Audits).
  • Section: 11 CCR § 7123(c)(18) Business Continuity and Disaster Recovery Plans, one of the 18 components in § 7123(c) Scope of Cybersecurity Audit and Audit Report.
  • Status: New. Added by the CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance regulations, effective January 1, 2026.
  • Who it applies to: Businesses whose processing of consumers' personal information presents significant risk to consumers' security under § 7120(b).
  • When it is assessed: If applicable. The auditor decides which § 7123(c) components apply to the business's information system (§ 7123(b)(2)), and the report must identify them (§ 7123(e)(2)).
  • Deadlines: First cybersecurity audit report due April 1, 2028, April 1, 2029 or April 1, 2030 depending on annual gross revenue (§ 7121). Certification of completion due by April 1 after each audit year (§ 7124).

Article 9 is not only about keeping personal information secret. § 7123(a) also covers protecting against unauthorized activity that results in loss of availability, such as ransomware. Component (18) is where continuity, recovery and backups come in.

The audit looks at business continuity and disaster recovery plans and at data recovery capabilities and backups. Testing incident response under § 7123(c)(17) and restoring from backups often go together in practice.

What Does CCPA § 7123(c)(18) Say?

The following is the text of 11 CCR § 7123(c)(18), shown with the § 7123(c) lead-in, from the final regulation text published by CalPrivacy and effective January 1, 2026. Only the formatting has been adjusted for readability.

  • (c) The cybersecurity audit must assess the following components, if applicable:
  • (18) Business-continuity and disaster-recovery plans, including data-recovery capabilities and backups.

Source: CalPrivacy, CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance Regulations (final regulation text). Authority cited: Section 1798.185, Civil Code. Reference: Section 1798.185, Civil Code.

How Does CCPA § 7123(c)(18) Map to the Secure Controls Framework (SCF)?

The SCF publishes a NIST IR 8477 Set Theory Relationship Mapping (STRM) between the CCPA as amended by the CPRA (statute and regulations as of January 2026) and SCF version 2026.3. It maps CCPA § 7123(c)(18) to 1 SCF control through 1 relationship (1 "subset of").

How to read the mapping: each relationship runs from the CCPA text to the SCF control. "Subset of" means the CCPA requirement is fully contained within the SCF control. The strength of relationship runs from 1 (nominal) to 10 (strongest), where 5 is moderately strong and 10 is typically reserved for "equal" and "subset of" relationships.

  • BCD-02 Business Continuity Management System (BCMS). Subset of (strength 10): 7123(c)(18). SCF control: Mechanisms exist to operate a Business Continuity Management System (BCMS) to achieve resilient Technology Assets, Applications, Services and/or Data (TAASD) during: (1) Routine operations; and (2) Adverse conditions.

Mapping taken from the STRM published with SCF version 2026.3. Download it at no cost: SCF STRM for the CCPA and CPRA (2026). The SCF explains the method in its Set Theory Relationship Mapping (STRM) guidance.

Common Pitfalls With CCPA § 7123(c)(18)

The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:

  • Backups never restored. A backup that has not been test-restored may not work when needed.
  • Backups reachable by attackers. Backups on the same network and credentials as production can be encrypted or deleted in the same attack.
  • Plans out of date. Continuity plans that do not reflect current systems and vendors are hard to execute.

What Is Reasonable Evidence for CCPA § 7123(c)(18)?

Article 9 does not publish a fixed evidence list. Under § 7122(d), audit findings must rely primarily on specific evidence such as documents reviewed, sampling and testing, and interviews, and under § 7122(g) the business and the auditor must keep all documents relevant to each audit for at least five years.

The SCF Evidence Request List (ERL) ties evidence artifacts to SCF controls. ERL items linked to the SCF controls mapped to CCPA § 7123(c)(18) include:

  • E-BCD-01 Continuity of Operations Plan (COOP). Documented evidence of a Continuity of Operations Plan (COOP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards. This involves internal and external stakeholders for incident response, disaster recovery and business continuity support requirements.

Records specific to CCPA § 7123(c)(18) that typically show the requirement is met:

  • Business continuity and disaster recovery plans. Current plans with roles, priorities and recovery objectives.
  • Backup configuration. Backup scope, frequency and protection such as immutability or isolation.
  • Restore tests. Records of test restores and recovery exercises.
  • Plan reviews. Periodic review and update records.

Which ComplianceForge Documents Support CCPA § 7123(c)(18)?

ComplianceForge documentation helps a business build and document the cybersecurity program the audit assesses. Under § 7122(a)(2), the auditor itself must not prepare the business's documents or implement its program. The following documents support CCPA § 7123(c)(18):

Frequently Asked Questions (FAQ)

Does the CCPA require backups? The cybersecurity audit must assess, if applicable, business continuity and disaster recovery plans, including data recovery capabilities and backups (§ 7123(c)(18)).

Why does availability matter for CCPA cybersecurity? § 7123(a) requires the audit to assess how the program protects against unauthorized activity resulting in the loss of availability of personal information, such as ransomware.

Does the CCPA require testing of backups? Article 9 does not set a test frequency, but data recovery capabilities are part of the assessment, and restore tests are common evidence that they work.

How does this relate to incident response? Incident response under § 7123(c)(17) covers recovering from malicious attacks, and continuity and recovery plans provide the means to restore operations and data.

Bottom Line on CCPA § 7123(c)(18)

Availability is part of security under Article 9. Keep continuity and recovery plans current, protect backups from the attacks they are meant to survive, and prove that restores work.

Authoritative sources:

This page reproduces California regulatory text from Title 11 of the California Code of Regulations. It is educational, not legal advice. Last reviewed: 2026-11-16.

Other CCPA Article 9 Requirements

Previous: § 7123(c)(17) Incident Response Management. Next: § 7124 Certification of Completion. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.