Most security teams picture their first California audit ending in a verdict. Pass, or pass with findings.

That is not what the rule asks for. It asks for a written account of your year.

Every gap the auditor finds, every fix, every incident and every notification you sent in 2027 has a place in that account. If the record of it does not exist, the report has nothing to be written from.

What does the first CPPA cybersecurity audit report cover, and who receives it?

For businesses whose annual gross revenue for 2026 was over $100 million, measured as of 1 January 2027, the timing is set by section 7121(a)(1). The first report is due "April 1, 2028," and the audit "would cover the period from January 1, 2027, through January 1, 2028."

That period opens in about two months.

The regulations define the cybersecurity audit report as "the document that every business must create as part of its cybersecurity audit" (section 7001(l)). Its contents are fixed by section 7123(e).

The rule sends the report inside the business. Section 7122(f) says it "must be provided to a member of the business's executive management team who has direct responsibility for the business's cybersecurity program."

What goes to the California Privacy Protection Agency is a separate certification of completion under section 7124, submitted via cppa.ca.gov "no later than April 1 following any year that the business is required to complete a cybersecurity audit." The executive signs it under penalty of perjury (section 7124(d)(4)).

Scope tests, the 18 components and what must already be running on 1 January are covered in our earlier piece on the 2027 audit period. This article is about the document at the end.

Why is the report a detailed account of your program, not a pass/fail opinion?

Read section 7123(e) as a table of contents. It has ten items, and none of them is a rating.

Item (1) requires the report to "describe the business's information system" and identify the policies assessed, the criteria used, and "the specific evidence examined to make decisions and assessments, such as documents reviewed, sampling and testing performed, and interviews conducted."

Then the auditor must "explain why" those policies, criteria and evidence "justify the auditor's findings."

Item (2) goes further. For each applicable component, the report must "describe how the business implements and enforces compliance" and "explain their effectiveness in preventing unauthorized access, destruction, use, modification, or disclosure of personal information."

That is narrative, not a checkbox. The auditor has to write how your multi-factor authentication, your patching and your log monitoring actually worked across the period.

The yardstick is proportional. Section 7123(b)(1) frames the program as one "appropriate to the business's size and complexity and the nature and scope of its processing activities, taking into account the state of the art and cost of implementing the components."

So the report will not just say whether a control exists. It will say whether it was right for you, and how the auditor knows.

What happens to a gap the auditor finds partway through 2027?

Item (3) is the one to plan around. The report must "identify and describe in detail the status of any gaps or weaknesses" that the auditor deemed to increase the risk to consumers' personal information.

The operative word is status.

Item (4) then requires the report to "document the business's plan to address the gaps and weaknesses identified and described pursuant to subsection (e)(3), including the timeframe in which it will resolve them."

Two practical readings follow.

→ An open gap needs a remediation plan and timeframe that someone in the business owns. The auditor documents it. The business writes it.

→ A gap found in May and closed in September does not vanish because it is closed. It still has a status. The cleanest way to describe that status is a dated trail: when it was found, what the risk was, what changed, when, and how the fix was verified.

If the only record of the fix is a ticket closed with "done," the auditor has an assertion. Section 7122(d) is explicit that findings may not "rely primarily on assertions or attestations by the business's management."

The trail is what turns your fix into evidence.

Which 2027 security incidents and breach notifications end up inside the report?

Start with the definition. For incident response, section 7123(c)(17)(A) defines a "security incident" broadly. It includes an occurrence that "actually or imminently jeopardizes the confidentiality, integrity, or availability" of the information system or the personal information it holds, or "that constitutes a violation or imminent threat of violation of the business's cybersecurity program."

That last limb matters. A policy breach with no data loss can still be a security incident in this frame. Your incident register needs to catch those, not only the events that reached legal.

Two report items then pull notifications into the document.

Item (9), consumer notices. If the business "provided notification to affected consumer(s) pursuant to Civil Code section 1798.82, subdivision (a)," the report must include "a sample copy of the notification(s), excluding any personal information; or a description of the notification(s)."

Item (10), agency notices. If the business "was required to notify any agency with jurisdiction over privacy laws in California," the report must include a sample copy or description, "the date(s) and details of the activity that gave rise to the required notification(s), and any related remediation measures taken by the business."

Note the different triggers. Item (9) turns on notices the business actually provided. Item (10) turns on notices it "was required" to make.

A DPO should read that second trigger closely. On the text, an agency notice that was required but not made does not drop out of item (10). It still has dates, details and remediation that the report must describe.

What must you hand the auditor, and what does holding something back cost you?

Section 7122(b) requires the business to "make available to the auditor all information in the business's possession, custody, or control that the auditor requests as relevant to the cybersecurity audit." The rule's own examples include information about "the business's use of service providers or contractors."

Section 7122(c) adds a good-faith duty: the business "must make good-faith efforts to disclose to the auditor all facts relevant to the cybersecurity audit and must not misrepresent any fact relevant to the cybersecurity audit."

Then comes the auditor's side. Item (8) requires a statement "signed and dated by the highest-ranking auditor" certifying that they "did not rely primarily on assertions or attestations by the business's management."

Put those together. An incident you kept off the register, or a vendor whose access you could not evidence, does not just weaken a finding. It sits under a signed auditor statement and, separately, the executive's own certification to the Agency under section 7124(d)(4), which includes a declaration that "the business has not made any attempt to influence the auditor's decisions or assessments."

Independence rules themselves are covered elsewhere. The point here is narrower: what you cannot produce, the auditor cannot write.

How does the first report constrain every report after it?

Item (5) requires each report to "identify any corrections or amendments to any prior cybersecurity audit reports."

For the first report, there is no prior report. For every report after it, the first one is the baseline.

That makes the first report hard to walk back. A component described as effective in the 2027 report, which later turns out to have been mis-scoped, becomes a correction that a later report has to name.

Item (6) adds role accountability: "the title of up to three qualified individuals responsible for the business's cybersecurity program." Titles, not names. Decide early which roles those are, so the 2027 evidence actually shows those roles owning the program.

What should your evidence record look like on 1 January 2028 so the report can be written from it?

The audit period closes on 1 January 2028. From that point, the report is an act of description.

If the record is complete, the auditor describes it. If it is not, the auditor describes the gaps in the record, under item (3).

Here is a mock table of contents built from section 7123(e), with the system of record that should feed each line.

Report item (7123(e))What it must containSystem of record that feeds it
(1) System, scope and evidenceInformation system description; policies, criteria and specific evidence examined; why they justify findingsAsset and data inventory; policy library; audit evidence log (documents, samples, interviews)
(2) Components and effectivenessApplicable components; how each is implemented and enforced; effectivenessControl register mapped to the 7123(c) components, with test results across the period
(3) Gaps and weaknessesDetailed status of each gap that increases risk to personal informationFindings register with dated status history
(4) Remediation planPlan to address each gap, with timeframeRemediation tracker with owner, target date and verification
(5) Prior-report correctionsCorrections or amendments to earlier reportsReport version history (empty in year one, the baseline after)
(6) Program ownersTitles of up to three qualified individualsGovernance record of program roles
(7) Auditor detailsName, affiliation, qualificationsEngagement file
(8) Auditor statementSigned, dated independence and no-primary-reliance statementEngagement file; evidence log proving reliance on evidence
(9) Consumer noticesSample or description of Civil Code 1798.82(a) noticesIncident register linked to notification log
(10) Agency noticesSample or description, dates, details, remediationIncident register linked to regulatory notification log and remediation tracker

Two rows carry most of the 2027 workload: the findings register for items (3) and (4), and the incident register for items (9) and (10). Both need to be dated from the first day of the period.

Section 7122(g) then requires the business and the auditor to "retain all documents relevant to each cybersecurity audit for a minimum of five (5) years after completion of the cybersecurity audit." The record you build in 2027 is the record you keep.

This is the shape Aigis is built around. Each 7123(c) component is traced to verbatim source text, so a control, its evidence and its gap status sit against the obligation they answer. When the auditor asks for item (3), gap status is a query, not a reconstruction. See how this supports audit teams, how gaps are tracked in risk management, and how the engine works on the platform.

Answer once. Assess everything.

FAQ: CPPA cybersecurity audit report

Is the CPPA cybersecurity audit report filed with the California Privacy Protection Agency? The rule sends the report to "a member of the business's executive management team who has direct responsibility for the business's cybersecurity program" (section 7122(f)). What the Agency receives is a written certification of completion under section 7124, submitted via cppa.ca.gov.

Does a gap that was fixed during 2027 still appear in the report? Item (3) requires the report to "describe in detail the status of any gaps or weaknesses" the auditor deemed to increase risk. A closed gap still has a status. Keep a dated trail so that status can be shown with evidence rather than asserted.

What counts as a security incident for the audit? Section 7123(c)(17)(A) includes any occurrence that "actually or imminently jeopardizes" the confidentiality, integrity or availability of the information system or the personal information it processes, and any "violation or imminent threat of violation of the business's cybersecurity program."

Who is named in the report? Up to three qualified individuals responsible for the program, by title (item (6)), and the auditor by name, affiliation and qualifications (item (7)).

See which 7123(e) items your current records can already feed at agrc.ai.