Purpose
This policy establishes the framework for business continuity management at Carriyo. It ensures that critical business functions can continue during and after a disruption, minimizing impact on our customers and operations.
Scope
This policy covers all Carriyo operations, systems, and processes that are essential to delivering our platform services.
Key Commitments
Service Level Objectives
- Uptime SLA: Carriyo's platform availability commitment is defined in CAR-ISMS-POL-001 (the single authoritative source for this figure).
- Recovery Objectives (RTO/RPO): Carriyo applies the tiered recovery model defined in the IT Disaster Recovery Policy (CAR-ISMS-POL-013):
- Tier 1 — Critical (core API, shipment processing, database clusters): RTO 1 hour / RPO 15 minutes
- Tier 2 — Important (dashboard, reporting, webhook delivery): RTO 4 hours / RPO 1 hour
- Tier 3 — Standard (internal tools, non-customer-facing and staging services): RTO 24 hours / RPO 24 hours
Redundancy
- Carriyo's primary production region is AWS eu-west-1 (Ireland)
- Multi-availability zone (multi-AZ) deployment across cloud infrastructure within the primary region
- Default disaster recovery is automatic in-region, multi-AZ failover — Carriyo does not fail over to another region by default
- Database replication with synchronous writes within the primary region (Multi-AZ) and automated multi-AZ failover
- Multi-region set-up: A multi-region set-up is offered to customers as an option; no customer is on it today and no second region is deployed. Continuity rests on the multi-AZ deployment in AWS eu-west-1; the option is engineered when a customer subscribes and documented at that time
Business Impact Analysis
Carriyo conducts an annual Business Impact Analysis (BIA) to identify:
- Critical business processes and their dependencies
- Maximum tolerable downtime for each process
- Required resources for recovery
- Interdependencies between systems and services
Continuity Plans
Infrastructure Failure
- Automated failover across availability zones within the primary region (default for all customers)
- Load balancer health checks with automatic traffic rerouting
- Container orchestration with automatic pod rescheduling
- Should a customer take the multi-region option, the cross-region runbook is added to the IT Disaster Recovery Plan (CAR-ISMS-PRC-003) at that time
Data Loss
- Continuous database replication
- Point-in-time recovery capability
- Regular backup testing and validation
- Encrypted off-site backup storage
Security Incident
- Incident response procedures as defined in the Incident Management Policy
- Communication plans for customer notification
- System isolation and recovery procedures
Vendor Failure
- Critical vendor dependencies are identified and monitored
- Alternative vendors are identified for essential services
- Vendor SLAs are reviewed annually
Testing
Business continuity plans are tested at least annually through:
- Tabletop exercises simulating various disruption scenarios
- Technical failover testing for critical infrastructure
- Backup restoration validation
- Communication plan testing
Review
This policy and associated continuity plans are reviewed annually or following any significant incident or change to Carriyo's infrastructure.
Document Control
| Version | Date | Author | Change |
|---|---|---|---|
| 1.0 | 2025-01-01 | Seth | Initial version. |
| 1.1 | 2026-06-25 | Seth | Reconciled RTO/RPO to the tiered model in POL-013; clarified replication mechanism. |
| 1.2 | 2026-06-25 | Seth | Corrected the resilience/DR model: named the primary region as AWS eu-west-1 (Ireland); clarified that default DR is in-region multi-AZ failover and that cross-region failover is an optional paid opt-in service with a customer-chosen warm-standby secondary region (designated AWS us-east-2, Ohio). Approved by Joao Vieira (CISO). |
| 1.3 | 2026-06-30 | Seth | Availability commitment now references CAR-ISMS-POL-001 as the single authoritative source rather than restating the figure. DRAFT — pending Joao's approval. |
| 1.3 | 2026-10-06 | Joao Vieira | APPROVED by Joao Vieira in the ISMS portal on 2026-10-06 (per Stan, 2026-10-06); status Draft -> Active. No content change. |
| 1.4 | 2026-10-27 | Seth | CISO rulings of 2026-10-27 (Security/risk-scoring-decisions-2026-10-27.md §8, §10): the 'customer-chosen secondary region / us-east-2 warm standby' wording struck — multi-AZ in AWS eu-west-1 is the set-up as operated; a multi-region set-up is offered, deployed for no customer. No continuity requirement changed. v1.3 (Active) remains the published version until v1.4 is approved. |