AutoCore Backup Security and Retention
Documents database backup, encryption options, retention, and derived-state boundaries.
The database backup script produces a compressed pg_dump and supports GPG and optional R2 upload. Encryption at rest, off-host retention, access control, and restore testing remain deployment responsibilities unless verified in the target environment.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Scope | Back up authoritative PostgreSQL data and required configuration metadata; treat search as rebuildable. |
| Encryption | Use the documented GPG or storage encryption path; never upload an unencrypted backup as a normal process. |
| Retention | Apply an approved retention window and verify pruning does not remove the last usable restore point. |
| Access | Restrict backup artifacts, keys, logs, and upload destinations to named operators. |
| Testing | A backup is evidence only after a controlled restore or integrity check succeeds. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.