Izymes Business Continuity and Disaster Recovery Policy
1. Purpose
This policy defines Izymes’ approach to ensuring business continuity and recovering from disruptive events that may affect the company’s operations, software products, and services.
It aims to protect the interests of Izymes, its customers, and stakeholders by minimizing the impact of incidents and enabling timely recovery of critical functions.
2. Scope
This policy applies to:
- Izymes’ internal operations (development, support, and administration).
- Izymes’ Atlassian Marketplace apps, whether deployed:
- On-premises: Installed in customer-managed environments (behind customer firewalls).
- Cloud: Delivered as SaaS and hosted in AWS-managed environments.
- Support services delivered through Atlassian Jira Cloud.
- Source code and related artifacts maintained in Atlassian Bitbucket Cloud.
It does not extend to customer-managed infrastructure, where customers themselves are responsible for their own business continuity and disaster recovery.
3. Roles and Responsibilities
| Role | Responsibilities |
|---|---|
| CEO/Director | Ensures the existence and review of BCDR plans; oversees recovery efforts. |
| Engineering Team | Maintains source code, backups, and deployment mechanisms; supports recovery of cloud-hosted apps. |
| Support Team | Manages customer communications and support tickets via Jira Cloud during disruptions. |
| Customers | Responsible for the continuity and recovery of on-premises app deployments within their own environments. |
4. Critical Assets and Their Protection
| Asset | Hosting/Location | Responsibility | BCDR Measures |
|---|---|---|---|
| On-Premises Apps | Customer’s data center | Customer | Customers are responsible for hosting, backups, and DR of their environments. |
| Cloud-Hosted Apps | AWS (managed by Izymes) | Izymes | AWS infrastructure provides redundancy; regular monitoring, automated failover where applicable, and periodic backups of essential app data. |
| Source Code | Atlassian Bitbucket Cloud | Izymes | Bitbucket Cloud provides high-availability and disaster recovery. Code also backed up periodically by Izymes. |
| Support System | Atlassian Jira Cloud | Izymes | Jira Cloud is maintained and backed up by Atlassian. Izymes monitors service health and retains critical communications outside Jira if necessary. |
5. Business Continuity Strategies
- Izymes maintains remote-friendly operations; all critical staff can work from any location with internet access.
- Cloud infrastructure (AWS) is designed for high availability, with services spread across multiple availability zones.
- For on-premises apps, Izymes provides guidance to customers on backups and disaster recovery but does not control or guarantee customer environments.
- Key documents and configurations are version-controlled and accessible by authorized personnel.
6. Disaster Recovery Procedures
For Cloud-Hosted Apps:
- Monitor AWS and Atlassian status pages for incidents.
- In the event of an AWS region failure, follow AWS failover procedures or restore services in a different region if applicable.
- Validate integrity of data from backups and restore if required.
For On-Premises Apps:
- Provide customers with documentation and support to reinstall or reconfigure apps if needed after a customer-side disaster.
For Internal Tools:
- Rely on Atlassian’s documented recovery procedures for Jira Cloud and Bitbucket Cloud.
- Keep periodic exports of critical data (e.g., support tickets) in secure storage for contingencies.
7. Testing and Review
- The BCDR policy and associated procedures will be reviewed annually.
- Internal recovery procedures for cloud-hosted apps will be tested at least annually or after major infrastructure changes.
- Customers are encouraged to test their on-premises recovery procedures independently.
8. Communication During Disruption
- Customers will be notified via email, status page, or Jira Service Desk if any service disruption occurs.
- Regular updates will be provided until the issue is resolved.
9. Policy Maintenance
This policy is owned by the Izymes CEO and reviewed annually or when significant changes to infrastructure, operations, or business models occur.
Effective Date: 1st July 2025
Next Review Date: 1st July 2026