Security
Backups are the last line of defense. Here's how Cloudhold protects them — and itself.
- Immutable snapshots: Content-hashed manifests with WORM semantics; no delete or update code path exists.
- Air-gapped copies: Complete and up: snapshots replicated to isolated object storage under object-lock, with credentials separate from production.
- API-key auth: Set CLOUDHOLD_API_KEY to require X-API-Key on every endpoint except /health, compared in constant time.
- Scoped restores: Restores are per-user and entitlement-checked; unauthorized items are denied and reported, never silently skipped.
- Env-only secrets: Connector tokens and API keys live in environment variables; structured logs never include payload data.
- TLS at the edge: Terminate TLS at your reverse proxy; the API binds loopback by default.
Known limits (we'd rather you read them here)
- The v1 store is local disk; the S3 Object Lock backend is the launch milestone.
- Anomaly detection flags likely mass-encryption — it is not malware removal.
Questions or a vulnerability to report? Contact us — security reports go to the top of the queue.
