Audit Evidence Pack
Maps Clone audit logs, approvals and controls to your own SOC 2, HIPAA, ISO 27001, NIST 800-53 or CMMC audit so AI teammates are audit-ready.
What this is for
Once Clones act in your systems, your auditors will ask how those actions are controlled: who approved the access, what the Clone did, who reviewed it, and how changes were managed. This pack answers those questions in the language of the framework you are audited against. It maps Clone audit logs, approval records, access settings and change control to your controls, and lists exactly where each piece of evidence comes from.
This pack supports your organization's audits. It is not a statement about Clone's own certifications. Clone's position today: GDPR in place, BAAs available, SOC 2 Type I/II in progress, ISO 27001 and ISO 42001 targeted. Our DPA, BAA, security whitepaper and compliance status are in the vendor security package. Control references below are illustrative starting points; your auditor and compliance team decide the applicable controls and the sufficiency of evidence. Not legal advice.
When to use it
Start it in Month 7, once Clones act within limits in production. Refresh it before every audit period and after any material change to Clones, connections or autonomy levels. It becomes part of the handoff to your CoE.
Who's involved
- GRC Specialist owns the pack and works with your compliance team.
- InfoSec lead confirms controls and signs.
- Compliance or internal audit lead confirms framework scope and evidence format.
- Org admin exports logs and access reports.
- IT lead supplies change and identity evidence.
How to fill it in
- Confirm the frameworks in scope and the audit period with your compliance lead (section 1).
- Confirm which Clones, connections and data are in audit scope. For HIPAA, note which Clones touch ePHI; for CMMC, note whether any Clone is in the CUI boundary.
- Work through the control mapping (section 2). Keep the rows that apply; add your own control IDs.
- For each row, record the evidence artifact, where it comes from and who produces it.
- Collect and index the evidence (section 3). Use tamper-evident audit log exports for the period.
- Run the pre-audit checklist (section 4) and log any gaps with owners (section 5).
The template
1. Scope
| Field | Entry |
|---|---|
| Frameworks in scope | SOC 2 (Security, Confidentiality); HIPAA Security Rule |
| Audit period | 1 Jan – 31 Dec |
| Auditor / assessor | |
| Clones in scope | Support Triage Clone, Billing Clone, Intake Clone (ePHI) |
| Connected systems in scope | Helpdesk, ERP, EHR intake portal |
| Data classifications in scope | Confidential, ePHI |
| Clone vendor documents provided | DPA, BAA, security whitepaper, compliance status |
| Compliance lead |
2. Control mapping
Illustrative mapping. Confirm control IDs and wording against your framework version and your auditor's expectations.
| Control area | What the auditor asks | Clone evidence | SOC 2 (TSC) | HIPAA Security Rule | ISO 27001:2022 Annex A | NIST 800-53 Rev. 5 | CMMC L2 |
|---|---|---|---|---|---|---|---|
| Logical access and authentication | Who can use and administer Clones; is SSO enforced? | SSO configuration; org roles and user list export; custom role definitions | CC6.1, CC6.2 | 164.312(a)(1), 164.312(d) | 5.15, 5.16, 8.5 | AC-2, IA-2 | AC.L2-3.1.1, IA.L2-3.5.3 |
| Least privilege for Clones | Are Clone connections scoped to the job? | Connections & Permissions Plan; connection scopes per Clone; InfoSec approval records | CC6.3 | 164.308(a)(4) | 5.18, 8.2 | AC-6 | AC.L2-3.1.5 |
| Access reviews | Is access reviewed periodically? | Quarterly access review record for users, admins and Clone connections | CC6.2, CC6.3 | 164.308(a)(3)(ii)(B) | 5.18 | AC-2(3), AC-6(7) | AC.L2-3.1.1 |
| Audit logging | Are Clone actions logged with who, what, when? | Clone audit log configuration; sample log entries; tamper-evident export | CC7.2 | 164.312(b) | 8.15 | AU-2, AU-3, AU-12 | AU.L2-3.3.1 |
| Log review | Does someone review the logs? | Monthly audit log review notes; override and exception reviews | CC7.2, CC7.3 | 164.308(a)(1)(ii)(D) | 8.16 | AU-6 | AU.L2-3.3.5 |
| Log protection | Can logs be altered? | Tamper-evident export; storage location and retention setting | CC7.2 | 164.312(c)(1) | 8.15 | AU-9 | AU.L2-3.3.8 |
| Human oversight of automated actions | Who approves what a Clone does? | Autonomy level per workflow; approval history; Governance Charter "never allowed" list | CC5.2, CC7.2 | 164.308(a)(1)(ii)(B) | 5.1, 8.16 | AC-5, CA-7 | AC.L2-3.1.4 |
| Change management | How are Clone skills and configurations changed? | Skill version pinning; test pack results; change log with approver and rollback version | CC8.1 | 164.308(a)(8) | 8.32 | CM-3, CM-4 | CM.L2-3.4.3 |
| Risk assessment | Are AI risks assessed and tracked? | AI Risk Register with owners, mitigations and review dates | CC3.2, CC3.4 | 164.308(a)(1)(ii)(A) | 5.7 (and 6.1.2 clause) | RA-3 | RA.L2-3.11.1 |
| Incident response | How are Clone incidents handled? | Incident log; demotion records; post-incident reviews | CC7.3, CC7.4 | 164.308(a)(6) | 5.24, 5.25, 5.26 | IR-4, IR-6 | IR.L2-3.6.1 |
| Vendor management | Is the AI vendor assessed and contracted? | Vendor security package; DPA; BAA where applicable; vendor risk review record | CC9.2 | 164.308(b)(1) | 5.19, 5.20, 5.23 | SA-9, SR-6 | (per scoping) |
| Policy and acceptable use | Is AI use governed by policy? | AI Use Policy; training completion records | CC1.4, CC2.2 | 164.308(a)(5) | 5.10, 6.3 | PL-4, AT-2 | AT.L2-3.2.1 |
| Data handling and retention | What data do Clones hold and for how long? | Data flow table from the Integration Architecture; retention settings | C1.1, C1.2 | 164.310(d)(2), 164.312(c)(1) | 5.12, 8.10 | MP-6, SI-12 | MP.L2-3.8.3 |
3. Evidence index
| # | Evidence | Control rows | Source | Period covered | Produced by | Date collected | File / link |
|---|---|---|---|---|---|---|---|
| E-01 | Audit log export, all in-scope Clones | Audit logging, Log protection | Clone audit log (tamper-evident export) | Q1–Q4 | Org admin | ||
| E-02 | Quarterly access review: users, admins, Clone connections | Access reviews | Portal + identity provider | Q3 | IT lead | ||
| E-03 | Autonomy promotion evidence packs | Human oversight | Portal autonomy history | Period | GRC Clone | ||
| E-04 | Skill change log with test results | Change management | Change control log | Period | Lead builder | ||
| E-05 |
4. Pre-audit checklist
- Every in-scope Clone has a Governance Charter entry with permitted data, permitted actions and "never allowed"
- Every in-scope connection has an InfoSec approval record and a current review date
- Audit logs exported for the full period, with integrity verified
- Monthly log reviews documented for every month in the period
- Every autonomy promotion in the period has a pack with both InfoSec and business owner sign-off
- Every production skill change has a test result, approver and rollback version
- AI Risk Register reviewed within the period
- Incidents in the period have post-incident reviews
- Vendor documents (DPA, BAA if applicable, whitepaper, compliance status) on file and current
- AI Use Policy acknowledged and training records available
- Evidence index reviewed by the compliance lead
5. Gaps and remediation
| # | Gap | Control row | Risk | Remediation | Owner | Due | Status |
|---|---|---|---|---|---|---|---|
| 1 | Two monthly log reviews missing (Jun, Jul) | Log review | Medium | Back-review with notes; add reminder to CoE rhythm | InfoSec lead |
Good looks like
- The mapping uses your control IDs and your auditor's language, confirmed before collection starts.
- Evidence covers the full audit period, not a snapshot taken the week before fieldwork.
- Human oversight is shown with records, not descriptions: approvals, sign-offs, sampled reviews.
- Gaps are found by you before the auditor finds them, and each has an owner.
- Vendor claims are stated accurately. Clone's SOC 2 and ISO work is described as in progress or targeted, never as a held certification.
- Common mistake: treating Clones as a single "system". Auditors want per-Clone scope, access and logs.
How Clone helps
The GRC Clone drafts the mapping for your frameworks, assembles the evidence index from audit log exports, approval records, autonomy history and the change log, and flags missing months or unsigned packs. The Project Clone tracks remediation items in the portal. The GRC Specialist reviews everything with your compliance lead. The routine is handed to your CoE so each audit cycle runs without us.
Sign-off
| Role | Name | Date | Decision |
|---|---|---|---|
| InfoSec lead | Approved for audit use | ||
| Compliance / internal audit lead | Scope and mapping confirmed | ||
| GRC Specialist | Assembled and verified |