CONFIDENTIAL — Shared under mutual NDA. Do not distribute outside your organization.
Business Continuity & Disaster Recovery Policy
CloudFive · Effective: June 2026 · Owner: Todd Densmore · Review: Annual
1. Purpose
This policy defines how CloudFive maintains service continuity and recovers from disruptive events including
infrastructure failures, data loss, and personal incapacitation. Given CloudFive's structure as a single-operator
consultancy, this policy prioritizes transparency with clients when disruptions occur.
2. Recovery Objectives
| System / Data | RPO (max data loss) | RTO (max downtime) |
|---|
| Client-managed AWS infrastructure | 24 hours (daily backup) | 4 hours |
| Source code (GitHub) | 0 (push on commit) | 1 hour |
| CloudFive internal systems | 24 hours | 8 hours |
| Secrets & credentials | 0 (1Password sync) | 1 hour |
3. Backup Strategy
- AWS RDS / databases: Automated daily snapshots retained for 30 days. Point-in-time recovery enabled.
- S3 data: Versioning enabled on all client data buckets. Cross-region replication for critical buckets.
- Infrastructure as code: All infrastructure defined in Terraform/CDK, committed to Git. Environment can be rebuilt from code.
- Credentials: Stored in 1Password with emergency kit secured offline.
- Development laptop: Time Machine to encrypted local drive + cloud backup. RPO: daily.
4. Scenario Responses
- AWS region outage: Restore from snapshots in secondary region. Estimated RTO: 4 hours.
- Data corruption: Restore from versioned S3 or RDS snapshot to the last known-good state.
- Ransomware: Isolate affected systems. Restore from immutable backups (S3 Object Lock where applicable). Do not pay ransom.
- Operator incapacitation (illness, emergency): Client is notified within 24 hours. Emergency contact (designated third party) has documented access to project repositories and credentials vault for continuity handoff.
5. Testing
- Backup restoration tested quarterly for active client environments.
- Infrastructure rebuild tested annually from IaC source (staging environment).
- Results documented and remediation tracked if gaps found.
6. Client Notification
CloudFive will notify affected clients within 4 hours of any disruption expected to exceed 2 hours for P1 clients,
or 24 hours for P2/P3 engagements. Notification includes estimated resolution time and status updates every 2 hours until resolved.
7. Contact
Todd Densmore — todd@cloudfive.net