RTO, RPO and the restore test almost nobody has run
Most teams have backups and no idea how long a restore takes. Set recovery targets per service, prove them with a quarterly restore test, and write the plan so it fits on one page.
Blog
Resilience and continuity
Articles about Resilience and continuity from the ConsultorIA blog: cloud, applied AI and security in production.
Multi-region is a cost decision before it is an architecture decision
Cold, warm and hot standby differ by an order of magnitude in price and by minutes or hours in recovery. Pick the tier from what an outage actually costs you, and be honest that most estates should buy multi-zone instead.
The runbook you use at 3am, not the one you show the auditor
Severity defined by criteria instead of instinct, three roles, one timeline and a named person who decides whether to notify. Everything else in an incident process is optional.
Your first five chaos experiments, and the ones to run in staging
Chaos engineering fails when it starts with a tool and a production cluster. Start with a hypothesis, a small blast radius and a stop condition, and the first five experiments will find something every time.
A backup the attacker can delete is not a backup
Ransomware crews go for the backups first, and cloud backups are easier to delete than tape ever was. Immutability, credential separation and a copy outside the blast radius are what turn a backup into a recovery.