AI Audit Exchange
Go back

Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

CPPA Cybersecurity Audit: What the Certification Cycle Requires of Your Evidence

What is a CPPA cybersecurity audit?

A CPPA cybersecurity audit is an audit under the California Privacy Protection Agency's cybersecurity-audit regime — one of the two regimes AI Audit Exchange supports, alongside SB 1119. On this platform a CPPA engagement gets its own evidence room, tagged with the CPPA regime and its audit period, with artifacts sealed at intake and a manifest the auditor can verify independently.

Certification is a claim; the audit tests the claim

A certification cycle creates a particular kind of pressure: the organisation states, formally, that its cybersecurity programme meets the regime's expectations, and the audit exists to test whether the evidence supports that statement. That means the auditor's questions are never really about the policy document. They are about the artefacts underneath it — the records showing the practice operated, during the period, in the way the policy describes. When the evidence is thin, the conversation becomes about your filing, not your security. A complete room keeps the conversation where it belongs.

The phase-in dates, at the confidence the sources support

As reported in concordant law-firm secondary sources — primary gazette texts not opened by us, and stated at that confidence level — CPPA cybersecurity-audit certifications phase in from 1 April 2028. A phase-in rewards early filers twice: the first cycle's evidence is gathered while the practices are current, and the room structure built for cycle one becomes the template every later cycle reuses. The wider calendar, including SB 1119's 2029 date and the auditor-registry framework, is laid out in the 2028–2029 California AI audit timeline. Confirm your own obligations and dates with counsel; this platform makes no legal determination about any customer's duties.

What a CPPA room should hold

Hold what the examination will ask for: the period's security-relevant records and the suite evidence that bears on them. On this platform the importable evidence comes from ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock, imported read-only and unchanged, each artifact badged with its source product. Material no suite product produced can be filed as a direct upload, badged as such, so the auditor always knows the provenance of every file: generated by a named product, or uploaded directly by the auditee. The detailed filing list is in what evidence a CPPA audit needs.

Freshness: evidence has a shelf life

The platform's validation applies a stated freshness rule: an artifact is flagged stale when its recorded date falls more than 365 days before the validation run. That rule exists because cybersecurity evidence ages badly — a control record from three cycles ago says little about this period's practice. Run validation before the auditor arrives, read the stale flags as a work list, and file the current period's artifacts so the room demonstrates continuity rather than a single heroic snapshot. The rule and how to work it are covered in the freshness rule guide.

Questions, answers and the record of both

Audits generate questions, and where those questions live matters. Inside a room, an auditor can raise a question against the engagement and the auditee answers it in the same place, so the exchange becomes part of the retained record instead of a lost email thread. When the auditor's work is done, the room closes out the way every room should: manifest exported, retention set for the long term, access grants reviewed. If a successor auditor takes the next cycle, handover is a new scoped grant on a complete room — not a zip file and a prayer. See the questions-and-answers workflow.

Retention across cycles

Certification cycles repeat, and each cycle's record must survive into the next ones: a question in cycle three can reach back to cycle one's evidence. Free rooms retain for 12 months, which covers a single cycle's working life; paid plans allow retention up to 10 years per room so earlier cycles remain examinable. Set retention when the room is created, not when the disk warning arrives — and use a legal hold on any room whose deletion must be blocked outright. One room per period, each with its own retention setting, is the structure that makes a multi-cycle history readable.

Five actions to take

  1. Open a separate CPPA room for each audit period — never mix two cycles in one room.
  2. Import suite exports unchanged during the period, not in a rush at its end.
  3. Run the room's evidence validation before the auditor starts and clear every stale flag you can.
  4. Keep auditor questions and your answers inside the room so the exchange is part of the record.
  5. Set retention up to 10 years on paid plans for completed cycles, and export the manifest at close-out.

Worked example

A fictional e-commerce company, Northgate Provisions, faces its first CPPA certification cycle for the 2028 period. Its IT lead opens a CPPA room in January and files monthly: 8 suite imports in the first quarter, 11 in the second, 9 in the third and 13 in the fourth — 41 artifacts, each sealed on arrival and badged by source. A pre-audit validation run flags 3 artifacts as stale under the 365-day freshness rule; all three are superseded by current-period records filed within the week.

The auditor works the room under a scoped grant, raises 6 questions inside it, and receives 6 answers in the same thread. At close-out the manifest export lists all 44 artifacts with hashes; the lead samples five hashes herself before signing off — five of five verify. Retention is set to 10 years, so when the next cycle's auditor asks how a control operated two cycles earlier, the answer is a room, not a reconstruction.

Frequently asked questions

When do CPPA cybersecurity audit certifications begin?

Concordant law-firm secondary sources report certifications phasing in from 1 April 2028. We state the date at that confidence level; confirm your own obligations with counsel, as this platform makes no legal determination about any customer's duties.

How is a CPPA room different from an SB 1119 room?

Structurally they are the same room; the difference is the regime tag and the audit period it serves. AI Audit Exchange supports exactly two regimes — California SB 1119 and CPPA cybersecurity audits — and each room belongs to one of them.

What does the freshness rule flag?

Validation flags an artifact as stale when its recorded date is more than 365 days before the validation run. It is a prompt to file current-period evidence, not a legal judgment about the artifact.

Can the auditor verify the evidence has not changed?

Yes. Every artifact is SHA-256 sealed at intake and listed with its hash in the room manifest. The auditor can re-verify any artifact's hash against the stored record at any time.

How long should a completed cycle's room be kept?

Paid plans allow per-room retention up to 10 years, which keeps earlier cycles examinable when later auditors reach back. Free rooms retain for 12 months.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: California SB 1119 AI Audit: A Plain-Language Preparation Guide · Next: How to Prepare for an Independent AI Audit

AI Audit Evidence Checklist for California Engagements · How Long Should You Keep AI Audit Records? · What Is a Legal Hold on Audit Evidence?