For some businesses, the first CCPA cybersecurity audit period begins Jan. 1, 2027. That means the evidence supporting the first audit begins being created during 2027, well before the first report and certification are due. California's final California Consumer Privacy Act (CCPA) regulations took effect Jan. 1, 2026, requiring certain businesses whose processing of personal information presents significant risk to consumers' security to complete annual cybersecurity audits. Covered businesses will need an independent auditor to evaluate applicable elements of the cybersecurity program using specific evidence, testing, sampling and interviews, and an executive will ultimately certify completion under penalty of perjury. For organizations in the first phase, 2026 is therefore the practical readiness year. The work should begin with applicability, scope, evidence and auditor independence, not with a last-minute request for documents.
What you need to know about CCPA cybersecurity audit readiness
Determine whether Article 9 applies
- A CCPA-covered business must complete an annual cybersecurity audit when either of the following conditions is met for the preceding calendar year:
- The business derives 50% or more of its annual revenue from selling or sharing consumers’ personal information.
- The business meets the CCPA annual gross revenue threshold and processed the personal information of 250,000 or more consumers or households, or the sensitive personal information of 50,000 or more consumers.
The current CCPA gross revenue threshold is $26.625 million, effective Jan. 1, 2025. It’s adjusted for inflation every odd-numbered year, so businesses should confirm the threshold in effect when making their 2027 applicability determination. The 2026 regulations also classify personal information of consumers whom a business knows to be less than 16 years of age as sensitive personal information, and provide that willful disregard of age is deemed actual knowledge. This may affect the 50,000-consumer calculation. The analysis should document how consumer counts were calculated, which data populations were included, and how acquisitions, subsidiaries and shared processing environments affect the conclusion.
Understand the phased deadlines
The final regulations replaced the earlier draft's general 24-month implementation period with a revenue-based phase-in:
Revenue threshold | First audit period | Report and certification due |
More than $100 million in 2026 annual gross revenue | Jan. 1, 2027-Jan. 1, 2028 | April 1, 2028 |
$50 million to $100 million in 2027 annual gross revenue | Jan. 1, 2028-Jan. 1, 2029 | April 1, 2029 |
Less than $50 million in 2028 annual gross revenue | Jan. 1, 2029-Jan. 1, 2030 | April 1, 2030 |
Source: California Code of Regulations, Title 11, Section 7121(a), Timing Requirements for Cybersecurity Audits and Audit Reports, effective Jan. 1, 2026.
After the phase-in, a newly covered business generally audits the next 12-month period and completes its report by April 1 of the following year. Successive audits are annual, so readiness must become a sustainable operating process rather than a one-time compliance project.
Expect an independent, evidence-based audit
The auditor may be internal or external but must be qualified, objective and independent. The regulations restrict the auditor from participating in activities that may later be audited, including developing procedures, preparing the business's documents, making cybersecurity program recommendations beyond articulating audit findings, or implementing and maintaining the program. Organizations using the same provider for readiness and audit work should define roles and safeguards carefully and may need separate teams or providers for remediation and the formal audit.
The practical challenge isn’t simply whether a control exists. It’s whether the organization can produce evidence showing that the control operated as intended throughout the audit period.
A key planning question
Who will help management prepare, who will remediate identified gaps and who will perform the independent audit? Those roles should be determined before readiness work begins, not after.
Audit findings cannot rely primarily on management assertions or attestations. They must be supported by specific evidence, including documents, interviews, sampling and testing. The report must describe the information system and audit criteria, explain the evidence supporting conclusions, identify gaps and weaknesses, document remediation plans and timelines, address prior findings, and include the auditor’s qualifications and signed certification of independence. The business and auditor must retain relevant audit documents for at least five years.
The practical challenge isn’t simply whether a control exists. It’s whether the organization can produce evidence showing that the control operated as intended throughout the audit period.
Scope extends beyond a framework checklist
Article 9 requires the auditor to assess the components of the cybersecurity program that the auditor deems applicable to the business's information system. Depending on the environment, those components may include authentication and phishing-resistant multifactor authentication, encryption, access and privileged account management, personal information and technology inventories, secure configuration, vulnerability scanning and penetration testing, logging and monitoring, data loss prevention, segmentation, security awareness and training, secure development, third-party oversight, retention and disposal, incident response, business continuity and disaster recovery.
The definition of an information system includes resources that process personal information or can provide access to it, whether or not the business owns those resources. Service providers and contractors must cooperate with the business's cybersecurity audit and make requested relevant information in their possession, custody or control available to the auditor. As a result, cloud platforms, outsourced operations, software providers and other third parties may be part of the audit universe and evidence plan. For many businesses, readiness will therefore depend on third-party evidence they don’t directly control. Organizations should identify those dependencies early and determine whether existing contracts, evidence-sharing processes and vendor-management practices will support the audit.
Existing work can be reused, but only after a gap analysis. The regulations expressly allow a business to use an audit, assessment or evaluation prepared for another purpose, including one based on the National Institute of Standards and Technology Cybersecurity Framework 2.0, if it meets all Article 9 requirements on its own or through supplementation. A SOC 2 report, ISO 27001 certification, internal audit, penetration test or regulatory assessment may reduce duplication, but none should be assumed to satisfy the CCPA requirements without a detailed crosswalk.
The practical question is therefore not, 'Do we already have a SOC 2 or ISO 27001?' but, 'Which Article 9 requirements are already supported by our existing assurance work, and where are the evidence gaps?'
Why CCPA cybersecurity audit readiness is important now
The regulation changes the focus from having security policies to demonstrating, through independent evidence, that applicable cybersecurity controls are implemented and operating effectively. The challenge isn’t simply whether a policy or control exists, but whether the organization can produce reliable evidence showing that it operated as intended. That distinction matters in large, distributed environments where personal information may be spread across hundreds of systems, business units, and vendors.
The financial consequences of cyber events also continue to rise. IBM's 2026 Cost of a Data Breach Report found that the average U.S. breach cost reached $11.5 million, while the global average reached $4.99 million, a 12% year-over-year increase globally. The CCPA audit is a compliance obligation, but the underlying disciplines, including current inventories, effective access controls, tested incident response and documented remediation, also reduce operational and financial exposure.
Executive accountability is another significant change from earlier drafts and makes CCPA cybersecurity audit readiness more than a chief information security officer (CISO) compliance exercise. The annual certification is submitted by a member of the executive management team who is directly responsible for cybersecurity audit compliance, has sufficient knowledge of the audit and has authority to certify. The attestation is made under penalty of perjury and includes a statement that the business didn’t attempt to influence the auditor's decisions or assessments. The California Privacy Protection Agency may also conduct announced or unannounced compliance audits, which makes defensible documentation and consistent execution important before the first filing date.
A scalable example
Baker Tilly helped a global investment firm establish a repeatable cybersecurity health-check process across more than 150 portfolio companies using a focused set of NIST Cybersecurity Framework controls, standardized evidence requests, interviews, risk and maturity ratings, scorecards and targeted reassessments for higher-risk organizations. This wasn’t a CCPA cybersecurity audit, but it illustrates a transferable readiness principle: scalability. Organizations with large numbers of systems, business units, portfolio companies or third parties don’t necessarily need to treat every element identically. A documented risk-tiering approach can help establish the audit universe, inform sampling and testing, standardize evidence collection and prioritize remediation where personal-information exposure is greatest.
Five questions to test your readiness
- Do we know whether Article 9 applies to us, and can we defend the revenue and consumer-count calculations supporting that conclusion?
- Can we identify the systems, vendors and data populations that would fall within the audit universe?
- For each applicable control, can we produce evidence showing that it operated consistently, not merely a policy saying it should?
- Have we separated readiness and remediation responsibilities from the independent audit role?
- Could the responsible executive review today's evidence and be comfortable ultimately making the required certification?
Steps to take now
Confirm applicability and assign ownership
Document the revenue and data-volume analysis, identify the executive who will own audit compliance and establish a cross-functional steering group that includes privacy, cybersecurity, legal, internal audit, technology, procurement, and business operations.
Define the audit universe
Build or validate inventories of personal information, applications, infrastructure, cloud services, service providers and contractors. Map where personal information is stored, processed, and accessed, then risk-tier systems and third parties based on volume, sensitivity, criticality, and exposure.
Crosswalk controls and evidence
Map existing frameworks, audits and certifications to every applicable Article 9 component. For each control, identify the owner, expected evidence, system population, testing method, sample approach and retention location.
Protect auditor independence
Separate readiness, control design, remediation, and formal audit responsibilities. Document reporting lines, decision rights and safeguards for internal auditors or external providers.
Perform a readiness assessment and evidence dry run
Test whether policies and controls are consistently implemented and operating effectively across systems, business units, and vendors. Verify that evidence is complete and reproducible, exceptions are tracked, and prior findings have documented remediation plans and dates. Resolve high-risk gaps before the audit period begins.
Build the annual operating model
Establish a calendar for control operation, evidence collection, interim testing, issue escalation, executive reporting, report completion, five-year retention, and the April 1 certification. A repeatable model will reduce disruption and support consistent conclusions in future audit cycles.
Not sure whether your current cybersecurity program and assurance activities will satisfy Article 9? A focused readiness assessment can help determine applicability, define the audit universe, map existing evidence to Article 9 requirements and identify gaps that should be addressed before the applicable audit period begins. Connect with us to discuss your readiness priorities.






