Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
What Evidence Does a CPPA Cybersecurity Audit Need?
Short answer
A CPPA cybersecurity audit needs evidence that your security practice operated as certified, during the period: the period's suite-produced records — decision and notice evidence, safety and guardrail evidence, provenance records, conformity material — imported unchanged and badged by source, plus the organisational documents no product produces, filed as direct uploads. Currency matters as much as coverage: validation's 365-day freshness rule should show a room speaking for the current period, and the manifest should let the auditor sample it all without asking you where anything lives.
What is CPPA evidence?
CPPA evidence is the artifact set filed in a CPPA-tagged evidence room on AI Audit Exchange for one audit period: suite imports from ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock, held read-only and unchanged with source badges and SHA-256 seals, together with direct uploads for organisational material. The platform hosts and organises the evidence; what the regime legally requires is determined by the auditor and your counsel, not by the platform.
Evidence of operation, not evidence of intention
A cybersecurity audit distinguishes between what an organisation says and what it can show. Policies state intentions; the audit weighs operation — records generated while the practice ran. Build the room accordingly: for each area the certification speaks to, the room should hold records produced during the period by the systems and processes themselves. On this platform those records arrive as suite imports: the producing products' own exports, sealed at intake, carrying their source badges. A room heavy on intention-documents and light on operational records reads, to an auditor, as an organisation describing itself. Aim for the opposite ratio.
The four suite sources and what each contributes
ReviewDesk — ADMT Decision Review contributes the decision and notice records: how automated decisions were reviewed and what notices accompanied them, which in a security examination evidences control over consequential processing. CompanionGuard contributes safety and guardrail evidence for companion-style systems. ProvenanceGuard contributes provenance records for generated content — who or what produced it, under what attestations. CRAClock contributes conformity-timing material. Each imports unchanged; the Exchange never generates any of these evidence types itself. If a source is missing from your room's manifest for a period in which that system operated, expect the question — and have the import, or the honest explanation, ready in the thread.
The direct-upload layer: organisational truth
Around the suite evidence sits the organisational layer only you can file: the period's adopted security policies as adopted (with their dates), signed approvals and attestations, records of reviews the organisation itself conducted, correspondence that forms part of the record. File these as direct uploads, badged as such — the badge is what allows the auditor to weigh them correctly as the organisation's own documents rather than system output. Keep this layer disciplined: every direct upload should be a document whose absence the auditor would notice. Uploads added 'for bulk' dilute the manifest and slow the sampling you want to speed up.
Currency: the freshness dimension
For a cybersecurity examination, when evidence is from matters nearly as much as what it is. Validation applies the 365-day freshness rule: artifacts recorded more than a year before the run are flagged stale. A CPPA room should reach the auditor with its flags worked — current-period records imported for every area, older material either superseded by current equivalents or individually explicable as legitimately long-lived. Run validation monthly so currency is a trend you manage, not a surprise you meet. The full rule is explained in the freshness rule guide.
Coverage across the period, visibly
The auditor's coverage question — does this evidence span the whole period or describe one good month? — is answered by the manifest before it is asked: import dates spread across the period, each source represented in each stretch of it. File monthly so the manifest draws that picture naturally. Where a gap is real — a system offline for a month, a product adopted mid-period — the honest move is to note it in the room's thread before the auditor finds the silence. Auditors trust rooms whose owners surface their own gaps; the discovery order is a credibility signal in every examination.
What this platform will not decide for you
This guide describes what a well-built CPPA room holds. It does not — and the platform does not — determine what the CPPA regime legally requires of your organisation, whether your evidence satisfies it, or whether you are certified-ready. Those judgements belong to your auditor and your counsel; the room checklists are organisational aids, labelled as such. The platform's contribution is deliberately narrower and entirely practical: whatever evidence the examination needs, it can be filed sealed, badged, manifested, current and retained — in one room, per period, ready to be sampled. Build that, and the substantive conversation starts from your strongest position.
Five actions to take
- File operational records, not just policies: the period's suite exports are the room's spine.
- Import all four sources that operated in the period — ReviewDesk, CompanionGuard, ProvenanceGuard, CRAClock — unchanged and badged.
- Keep the direct-upload layer lean and real: adopted policies with dates, approvals, attestations, review records.
- Work the freshness flags until the room speaks for the current period; explain any legitimately old artifact individually.
- Check the manifest monthly for period-wide coverage, and note real gaps in the room before the auditor finds them.
Worked example
A fictional home-security platform, Iron Gate Home Systems, builds its CPPA room for the 2028 period. Monthly filing produces 73 artifacts by November: 27 ReviewDesk, 18 CompanionGuard, 16 ProvenanceGuard, 5 CRAClock, and 7 direct uploads — the adopted security policy with its adoption date, two signed attestations, and four internal review records. A validation run flags 6 artifacts stale; five gain current-period successors within the week, and one — the founding security architecture record — is acknowledged in the thread as historical by nature.
The auditor's sampling plan, built from the manifest in her first session, draws 15 artifacts across all five sources and all four quarters. Her coverage note observes that import dates span the period without clustering — the sentence every auditee wants and only monthly filing earns. Nothing in the room was created for the audit; everything in it was filed during the period it evidences. That is the standard a CPPA room should meet.
Frequently asked questions
Does AI Audit Exchange decide what the CPPA requires?
No. The platform hosts and organises evidence and makes no legal determination about any customer's duties or compliance. Requirements are a matter for your auditor and counsel; the room is where the evidence lives.
Which single source matters most for a CPPA room?
None in isolation — the examination reads across sources. The discipline that matters is completeness: every suite product that operated in the period represented in the manifest, current, and sealed.
How current must CPPA evidence be?
Validation flags artifacts recorded more than 365 days before the run as stale. For a cybersecurity audit, treat flags as a worklist: file current-period equivalents so the room testifies about present practice.
Can policies be filed as direct uploads?
Yes — adopted policies are organisational documents and belong in the direct-upload layer, dated as adopted. Pair them with operational records; policies alone certify intentions, not operation.
What if a suite product was adopted mid-period?
File its exports from adoption onward and note the adoption in the room's thread. A explained partial coverage reads as honesty; a silent gap reads as an omission.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Organise AI Audit Evidence by Period · Next: What Evidence Does an SB 1119 Audit Need?
How to Export an Audit Room Manifest (and When) · Immutable Evidence Storage: Why It Matters for Audits · How to Verify an Artifact Hash in an Evidence Room