Clone Solutions
Template

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

  1. Confirm the frameworks in scope and the audit period with your compliance lead (section 1).
  2. 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.
  3. Work through the control mapping (section 2). Keep the rows that apply; add your own control IDs.
  4. For each row, record the evidence artifact, where it comes from and who produces it.
  5. Collect and index the evidence (section 3). Use tamper-evident audit log exports for the period.
  6. Run the pre-audit checklist (section 4) and log any gaps with owners (section 5).

The template

1. Scope

FieldEntry
Frameworks in scopeSOC 2 (Security, Confidentiality); HIPAA Security Rule
Audit period1 Jan – 31 Dec
Auditor / assessor
Clones in scopeSupport Triage Clone, Billing Clone, Intake Clone (ePHI)
Connected systems in scopeHelpdesk, ERP, EHR intake portal
Data classifications in scopeConfidential, ePHI
Clone vendor documents providedDPA, 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 areaWhat the auditor asksClone evidenceSOC 2 (TSC)HIPAA Security RuleISO 27001:2022 Annex ANIST 800-53 Rev. 5CMMC L2
Logical access and authenticationWho can use and administer Clones; is SSO enforced?SSO configuration; org roles and user list export; custom role definitionsCC6.1, CC6.2164.312(a)(1), 164.312(d)5.15, 5.16, 8.5AC-2, IA-2AC.L2-3.1.1, IA.L2-3.5.3
Least privilege for ClonesAre Clone connections scoped to the job?Connections & Permissions Plan; connection scopes per Clone; InfoSec approval recordsCC6.3164.308(a)(4)5.18, 8.2AC-6AC.L2-3.1.5
Access reviewsIs access reviewed periodically?Quarterly access review record for users, admins and Clone connectionsCC6.2, CC6.3164.308(a)(3)(ii)(B)5.18AC-2(3), AC-6(7)AC.L2-3.1.1
Audit loggingAre Clone actions logged with who, what, when?Clone audit log configuration; sample log entries; tamper-evident exportCC7.2164.312(b)8.15AU-2, AU-3, AU-12AU.L2-3.3.1
Log reviewDoes someone review the logs?Monthly audit log review notes; override and exception reviewsCC7.2, CC7.3164.308(a)(1)(ii)(D)8.16AU-6AU.L2-3.3.5
Log protectionCan logs be altered?Tamper-evident export; storage location and retention settingCC7.2164.312(c)(1)8.15AU-9AU.L2-3.3.8
Human oversight of automated actionsWho approves what a Clone does?Autonomy level per workflow; approval history; Governance Charter "never allowed" listCC5.2, CC7.2164.308(a)(1)(ii)(B)5.1, 8.16AC-5, CA-7AC.L2-3.1.4
Change managementHow are Clone skills and configurations changed?Skill version pinning; test pack results; change log with approver and rollback versionCC8.1164.308(a)(8)8.32CM-3, CM-4CM.L2-3.4.3
Risk assessmentAre AI risks assessed and tracked?AI Risk Register with owners, mitigations and review datesCC3.2, CC3.4164.308(a)(1)(ii)(A)5.7 (and 6.1.2 clause)RA-3RA.L2-3.11.1
Incident responseHow are Clone incidents handled?Incident log; demotion records; post-incident reviewsCC7.3, CC7.4164.308(a)(6)5.24, 5.25, 5.26IR-4, IR-6IR.L2-3.6.1
Vendor managementIs the AI vendor assessed and contracted?Vendor security package; DPA; BAA where applicable; vendor risk review recordCC9.2164.308(b)(1)5.19, 5.20, 5.23SA-9, SR-6(per scoping)
Policy and acceptable useIs AI use governed by policy?AI Use Policy; training completion recordsCC1.4, CC2.2164.308(a)(5)5.10, 6.3PL-4, AT-2AT.L2-3.2.1
Data handling and retentionWhat data do Clones hold and for how long?Data flow table from the Integration Architecture; retention settingsC1.1, C1.2164.310(d)(2), 164.312(c)(1)5.12, 8.10MP-6, SI-12MP.L2-3.8.3

3. Evidence index

#EvidenceControl rowsSourcePeriod coveredProduced byDate collectedFile / link
E-01Audit log export, all in-scope ClonesAudit logging, Log protectionClone audit log (tamper-evident export)Q1–Q4Org admin
E-02Quarterly access review: users, admins, Clone connectionsAccess reviewsPortal + identity providerQ3IT lead
E-03Autonomy promotion evidence packsHuman oversightPortal autonomy historyPeriodGRC Clone
E-04Skill change log with test resultsChange managementChange control logPeriodLead 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

#GapControl rowRiskRemediationOwnerDueStatus
1Two monthly log reviews missing (Jun, Jul)Log reviewMediumBack-review with notes; add reminder to CoE rhythmInfoSec 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

RoleNameDateDecision
InfoSec leadApproved for audit use
Compliance / internal audit leadScope and mapping confirmed
GRC SpecialistAssembled and verified