How long should we retain AI audit logs?

For relevant high-risk AI systems, EU AI Act Articles 19(1) and 26(6) set a minimum of six months for automatically generated logs under the provider or deployer’s control, unless applicable Union or national law provides otherwise. Your final period must also account for privacy, sector, national, contractual, and legal hold requirements.

What does “tamper-evident” mean for logs?

That unauthorized changes are detectable. Common approaches include append-only storage, hash chaining, and periodic integrity verification with retained reports.

Do we need to log model outputs and prompts?

Keep enough context to explain the decision and verify the control. Apply data minimization, redaction, hashing, or controlled references where full content would create unnecessary privacy or security risk.

How do we handle legal hold?

Define a retention override that prevents deletion for specified scopes, and ensure all hold actions are logged and approved.

What do auditors want to see in exports?

A scoped bundle of relevant records, the approved policy and configuration, a manifest, checksums, access and export history, and clear instructions for independent integrity verification.

Is seven years required for every AI audit log?

Seven years is an editable example in this template. Use it only when a documented legal, regulatory, contractual, or approved operational basis supports that period.

Policy template

Audit log retention policy template for AI systems

Descargue una plantilla de retención de registros de auditoría para sistemas de IA: alcance de eventos, plazos, retenciones legales, integridad, acceso, eliminación verificada y exportación de evidencias.

Set a defensible retention schedule and the controls that enforce it.

For compliance, risk, product, and ML ops teams shipping agentic Processes into regulated environments.

Última actualización: 16 jul 2026 · Versión v1.1 · Muestra ficticia. No asesoramiento legal.

Download retention policy template Solicitar paquete completo

Informar un problema: /contact

Contexto

Qué es este artefacto (y cuándo lo necesita)

Explicación mínima viable, escrita para auditorías, no para teoría.

This template records what constitutes an audit event, where the event is stored, when its retention clock starts, how long it remains available, and which approved requirement supports that period.

It also covers legal holds, verified deletion, vendor-managed copies, integrity checks, access boundaries, and the evidence retained after each control runs.

Lo necesita cuando

You operate AI systems whose decisions, approvals, tool calls, or data access must remain reviewable.
You are standardizing retention periods across agents, Processes, storage systems, and vendors.
You are preparing an EU AI Act, privacy, security, procurement, or internal audit review.

Common failure mode

Logs exist across several systems, while the organization has no approved event taxonomy, clock trigger, documented basis, legal hold procedure, deletion evidence, or independently verifiable export.

Lista de verificación

Criterios de exito

Los revisores de los criterios de aceptación realmente verifican.

The event taxonomy covers decisions, approvals, tool calls, data access, configuration changes, and administrative actions.
Every schedule row names its clock trigger, period, basis, system owner, and next review date.
Legal holds suspend scheduled deletion for a defined scope and retain approval and release evidence.
Deletion is monitored, failures are remediated, and each completed run produces an auditable report.
Integrity verification is documented and retained with the policy evidence.
Access control separates viewing, exporting, retention administration, and break-glass activity.
Vendor-managed records follow equivalent retention, hold, disposal, and export requirements.
Exports include a manifest, checksums, relevant records, and independent verification instructions.

Avance

Vista previa de la plantilla

Un extracto real en HTML para que sea indexable y revisable.

Template preview (excerpt)

## 5) Retention register
For every event class, record:
- Retention trigger and approved period
- Legal, regulatory, contractual, or operational basis
- Personal data fields and minimization controls
- Legal hold behavior and deletion method
- Evidence retained after disposal

## 10) Legal holds
- Hold authority and required approvers
- Scope identification method
- Release approval and disposal window
- Evidence: notice, actions, release, and disposal report

Descargue el artefacto completo

Cómo hacerlo

Cómo rellenarlo (rápido)

Entradas que necesita, tiempo para completar y un ejemplo resuelto en miniatura.

Entradas que necesita

A system and event inventory, including downstream and vendor-managed copies.
Applicable legal, regulatory, contractual, privacy, and records-management requirements.
Retention clock triggers, legal hold needs, and approved disposal methods.
Integrity controls, verification cadence, and failure escalation procedures.
Roles allowed to view, export, place holds, administer retention, and approve exceptions.

Tiempo para completar: 30–60 minutes for an initial draft, followed by owner review.

Mini example: retention register

EJEMPLO

Event class: Decision and approval records
Clock starts: Decision closure
Period: 7 years (illustrative)
Basis: [insert exact requirement or approved purpose]
Hold behavior: Suspend deletion for matching case IDs
Disposal proof: Approved report + exception list

Mapeo KLA

Cómo KLA lo convierte en evidencia gobernada

Vincula el artefacto con las funcionalidades del producto para facilitar la conversión.

Govern

Policy-as-code checkpoints that block or require review for high-risk actions.
Versioned change control for model/prompt/policy/Process updates.

Assure

Risk-tiered sampling reviews (baseline + burst during incidents or after changes).
Near-miss tracking (blocked / nearly blocked steps) as a measurable control signal.

Prove

Configurable retention schedules, integrity verification, and an append-only Audit Trail.
Evidence Room export bundles (manifest + checksums) so auditors can verify independently.

Recursos relacionados

Evidence pack checklist Human oversight playbook Post-market monitoring plan template Platform: append-only audit ledger