Resilience
Resilience
Recovery should be planned and tested in proportion to how critical a service is.
- Updated:
This page sets out the standards Vitalos works to and is putting in place. They are commitments, not certified controls.
Our standard is that:
- recovery requirements match data and service criticality: what can be restored, from where, how long it should take and who decides;
- a backup that has never been validated is not treated as proven recovery capability;
- every production release has a rollback or recovery plan, and a deadline is not approval to skip it;
- incidents are classified by severity, with immediate escalation and recovery first for critical events;
- live services have explicit ownership, monitoring and runbooks before service-level-backed operation begins.
Specific response targets belong in each service agreement; they are not promised generically here.