Jungle Tech Corporation – Backup & Data Recovery Policy

Version: 1.1 | Last Updated: April 3, 2026

1. Purpose

The purpose of this policy is to ensure that all critical Jungle Tech data—including AI models, 3D visualization assets, and source code—is backed up regularly and can be restored quickly in the event of a system failure, human error, or cyberattack.

2. Scope

This policy applies to all production data hosted in Azure, as well as critical business documents stored in Microsoft 365.

3. Roles and Responsibilities

Approval: Michael Estephan (CEO) is responsible for approving the budget for redundant storage and recovery infrastructure.

Execution: Michael Habashy (Lead DevOps & Security Engineer) is responsible for configuring backup schedules, monitoring success/failure logs, and performing quarterly restoration tests.

4. Backup Strategy (The 3-2-1 Rule)

Jungle Tech follows the industry-standard 3-2-1 rule:

3 Copies of Data: (1 Production + 2 Backups).

2 Different Media/Services: Utilizing Azure Disk Snapshots and Azure Blob Storage.

1 Offsite Copy: All backups are Geo-Redundant (GRS), meaning data is replicated to a secondary Azure region to ensure survival in the event of a regional disaster.

5. Protection of Backups (Immutability)

Encryption: All backups are encrypted at rest using AES-256.

Access Control: Access to delete backups is strictly restricted. Administrative accounts require MFA + Resource Locking to delete backup vaults, protecting against ransomware that targets backup data.

Immutability: Critical AI training data is stored in "WORM" (Write Once, Read Many) storage where possible to prevent unauthorized tampering or deletion.

6. Disaster Recovery (RTO & RPO)

Jungle Tech strives to meet the following targets during a recovery event:

Recovery Point Objective (RPO): Maximum of 4 hours of data loss.

Recovery Time Objective (RTO): Systems should be online and functional within 12 hours of a major disaster.

7. Testing and Validation

Quarterly Drills: Michael Habashy will perform a "Restore Test" every 90 days to ensure that backup files are functional and the recovery process is documented and repeatable.

Reporting: Results of these tests will be reviewed by Michael Estephan to ensure business continuity.