Audit Logs

Keep signed evidence of every Clonio run.

Clonio can produce audit artefacts for each run. These logs document what was executed, when it ran, which source and target were used, which configuration was applied, and whether the run succeeded.

Signed audit logs help you prove that the transferred dataset was processed through a reviewed configuration instead of an ad-hoc copy script.

What to keep

  • Signed audit artefact for compliance review.
  • Structured process log for debugging and run history.
  • The committed .cloning.yaml version used for the run.

Verification

Use the CLI verification command when you need to validate audit integrity offline:

clonio cloning:verify-audit path/to/audit.html

Keep audit outputs outside your source repository unless your compliance process explicitly requires committed artefacts.