Skip to main content

Audit Export

Audit Export​

Audit exports save security event history outside WordPress. They contain sanitized event rows and a manifest with the export range, row count, and integrity information. They are not a full website backup.

Before you start​

You need permission to manage Awthy reporting and an active export entitlement. Open Awthy → Reporting → Evidence and export. If the panel shows an upgrade or unavailable state, resolve that before configuring a destination.

Connect and check delivery​

  1. Choose a destination: Amazon S3 or Google Drive.
  2. Complete its setup and confirm it appears in Audit export.
  3. Check the next scheduled run shown in the panel.
  4. After it runs, inspect Recent audit export runs and the destination's last successful export.
  5. Confirm the package and manifest arrived in the destination you selected.

For example, use a dedicated folder or bucket prefix named store-audit/ so exports are easy to distinguish from other backups. A saved destination alone does not show that an export has succeeded.

If delivery fails​

Review the visible run error, the destination settings, and any required Hub connection. Do not send provider credentials or raw export packages to support. Use the configuration report and the failed run's time and safe error message.

Disconnecting a destination removes its saved credentials and stops its scheduled exports. It does not remove packages already delivered to your storage.

Reporting guides​

Last updated on