Your CCPA Cybersecurity Audit May Start January 1, 2027. Will Your Evidence Hold Up?
April 1, 2028 may sound far away. For businesses in the first CCPA cybersecurity audit tier, it isn’t. The first audit period runs from January 1, 2027 through January 1, 2028, which means the controls and evidence you will rely on in the audit need to exist during 2027 – not be pieced together after the fact in 2028. The real question is not whether you can point to a policy. It is whether you can show how the control actually worked during the period under review.
Who actually has to complete an audit?
At a high level, the annual cybersecurity audit requirement applies to businesses whose processing presents significant risk to consumers’ security. A business can meet that threshold in either of two ways:
- deriving 50 percent or more of annual revenue from selling or sharing personal information; or
- exceeding the applicable CCPA gross-revenue threshold (currently $26.625 million after CPI adjustment) and, in the prior year, processing the personal information of 250,000 or more consumers or households, or the sensitive personal information of 50,000 or more consumers.
The first audit deadlines are phased in by revenue:
| Annual gross revenue | Measured as of | First report due |
| Over $100 million (2026) | January 1, 2027 | April 1, 2028 |
| $50-100 million (2027) | January 1, 2028 | April 1, 2029 |
| Under $50 million (2028) | January 1, 2029 | April 1, 2030 |
After the first audit, the requirement is annual. Each year, a member of executive management must certify completion to the CPPA by April 1, under penalty of perjury.
What will the audit actually look at?
The audit looks at whether your cybersecurity program makes sense for your size, complexity, and use of personal information – and, more importantly, whether the program is actually implemented and enforced. Depending on your environment, the audit can cover up to 18 named components, including:
- authentication, including phishing-resistant MFA;
- encryption of personal information at rest and in transit;
- least privilege and privileged access management;
- personal information and asset inventories;
- secure configuration and patch management;
- vulnerability scanning and penetration testing;
- centralized audit logging and network monitoring (IDS/IPS, DLP);
- segmentation and secure development;
- service provider oversight;
- retention and secure disposal; and
- incident response and business continuity and disaster recovery.
The evidence bar is higher than a typical gap assessment
This is where the CCPA audit starts to feel different from a high-level maturity review. The auditor cannot simply accept management saying, ‘Yes, we do this.’ Conclusions have to be backed by specific evidence – documents, samples, testing, and interviews – and the auditor has to be able to explain why that evidence supports the conclusion.
If the auditor identifies a gap or weakness that increases cybersecurity risk, the report needs to describe it, its status, and the business’s plan and timeframe for addressing it. If you fix an issue during the audit period, that remediation should be supported by evidence showing the control was implemented and is operating afterward. The business and auditor also need to retain relevant audit documentation for at least five years.
Already have ISO 27001 or NIST work? That’s a head start, not necessarily the finish line.
The regulations let businesses use an existing audit or assessment if it meets the CCPA requirements on its own or with additional work. That is good news for organizations that already have ISO 27001, NIST CSF, SOC 2, or similar assurance work. The catch is that a framework crosswalk or maturity assessment may not have been scoped to the right personal-information systems, or may not include the level of sampling and evidence-based testing the CCPA audit calls for. The goal should be to reuse what is good, identify what is missing, and avoid starting over unnecessarily.
If your audit period starts January 1, the useful question to answer now is: if we tested the program using the CCPA audit standard today, where would the evidence break down? That is the purpose of Tevora’s CCPA Cybersecurity Audit Readiness Assessment. [Schedule a readiness scoping call.]
Readiness first, then the independent audit
The approach we are using with clients is straightforward: find the issues before the audit period, give the business time to address them, and then perform the independent audit.
Phase 1: Readiness assessment. Before the audit period begins, we define the systems and processes in scope, review the evidence that already exists, and test the applicable audit components using an audit-oriented approach. We identify the gaps; the client owns the remediation decisions and implementation, either internally or with another provider.
Phase 2: Independent audit. We perform the formal CCPA cybersecurity audit for the audit period and prepare the audit report that supports the executive’s Certification of Completion.
That separation matters. The regulations require the auditor to remain independent. If the same firm expects to perform the formal audit later, it should not design the client’s procedures, prepare the client’s documentation, or implement and maintain the controls it will ultimately assess. Our readiness work is therefore focused on assessment, evidence validation, and clearly stating findings – not building the fixes for the client. We evaluate and document independence again before the formal audit begins.
Quick answers
Does every gap have to be fixed before January 1, 2027?
No. The regulations do not say every gap has to be closed before the first audit period starts. They do require the audit report to address gaps or weaknesses the auditor determines increase cybersecurity risk, including their status and the business’s plan and timeline for addressing them. Practically, though, the earlier a material issue is fixed, the more time you have to show that the control is actually working before the audit period ends.
If we already have ISO 27001 or NIST assessments, do we really need more work?
Maybe – but not necessarily from scratch. Existing assessments can be a strong foundation, and the CCPA regulations allow other audit or assessment work to be used if it covers the applicable requirements, either on its own or with supplementation. The key question is whether that work gives the auditor the scope, evidence, sampling, and testing needed for the CCPA audit. A crosswalk alone may not.
Do we send the full cybersecurity audit report to the CPPA every year?
No. The annual submission is a Certification of Completion confirming that the required cybersecurity audit was completed and identifying the audit period. The full report is not routinely filed with that certification. However, the business and auditor must keep the relevant audit documentation for at least five years, and those records may be subject to production in connection with CPPA oversight or enforcement.
Where Tevora can help
For first-tier businesses, the clock starts January 1, 2027. That does not mean every control has to be perfect on day one. It does mean you want to know where the weak spots are before the audit period is underway. If a material gap is found and fixed during 2027, the remediation can improve the audit posture – but you still need evidence that the fix was implemented and had enough time to operate.
This is the kind of work Tevora already does every day: control-based assessments, evidence validation, technical testing, and audit. For CCPA, we see the cleanest path as:
- Readiness assessment (Q4 2026). We scope the systems that process personal information, test the applicable audit components against the evidence you already have, and identify readiness gaps before the audit period begins. We do not design or implement the remediation if we expect to serve as the independent auditor later.
- Independent audit (2027 audit period). We perform the formal CCPA cybersecurity audit and prepare the report that supports the executive Certification of Completion.
The point is not to redo work you have already completed. It is to find out, before the clock starts, whether that work will hold up when someone asks for the evidence, selects a sample, tests the control, and asks the control owner to explain how it actually works. That gives your team time to address issues while preserving the independence needed for the formal audit.
[Schedule a CCPA cybersecurity audit readiness call with Tevora.]
This article is provided for general informational purposes and does not constitute legal advice. Applicability determinations should be made in coordination with qualified privacy counsel. Primary reference: CPPA Final Regulations Text, 11 CCR §§ 7120-7124.

