Research topic
Resilience
Recovery starts with an independent control path.
Design and testing guidance for containment, restoration, and control-plane recovery under pressure.
View every topicFrom the desk
38 publicationsRoll out configuration changes as carefully as code
Flags, policy rows, generated files and customer settings triggered several global outages between 2024 and 2026. Seven primary incident reports show how each change slipped past its safeguards, and which controls their authors adopted afterward.
Find the AWS global control planes in your recovery path
Thirteen AWS control planes run in us-east-1 or us-west-2, and ordinary calls from other Regions still reach them. Audit runbooks, SDK settings and the last exercise, then swap each dependency for a data-plane operation.
Plan for an outage at your CDN or edge provider
When the CDN, WAF and edge provider fails, traffic can move to a regional WAF, a second CDN or the origin, and each keeps less protection. Decide early whether a second path is worth securing.
Find the Entra changes that Backup and Recovery cannot roll back
Microsoft Entra Backup and Recovery rolls listed properties back to a daily backup kept for seven days. Credentials, role assignments, owners and user consent stay in place, and an unscoped recovery can undo your own containment.
Plan Azure disaster recovery for a region without a pair
Thirteen Azure regions have no pair and eight more pair with a restricted-access region. This guide shows which built-in geo-redundancy disappears, what replaces it service by service, and how to choose the recovery region.
Restore EBS volumes at the speed your recovery plan assumes
A restored EBS volume is slow until every block arrives from S3. Price the provisioned initialization rate, fast snapshot restore credits and Regional limits as recovery-time arithmetic before an RTO depends on them.
Contain failures with cell-based architecture and shuffle sharding
Cells limit a failure to the tenants behind one partition only when routing, data and change delivery are partitioned too. Here is how to choose the key, size cells and check the shuffle-sharding arithmetic.
Design health checks that remove broken instances without causing outages
A health check is an automated decision to remove capacity. Keep load balancer checks local, learn what your platform does when every target fails, and set probe timing from documented defaults.
Plan for the backlog that follows a regional cloud outage
AWS fixed the DNS fault behind its October 2025 us-east-1 outage within three hours, yet recovery ran into the afternoon. Design retries, queues and capacity automation for that second phase.
Choose a multi-region database consistency model before you need failover
The replication model decides which writes survive a Region failure. Compare asynchronous and quorum options in DynamoDB, Aurora, Spanner and Cosmos DB by recovery point, write latency and the reconciliation each one leaves you.
Back up a Kubernetes cluster so workloads can actually be restored
A Kubernetes backup has to carry definitions, Secrets and volume data, and the restore depends on identity, keys and images it never held. Plan the layers, the restore order and the checks that prove recovery.
Prepare a cloud exit strategy that satisfies DORA
DORA requires a tested exit plan for every cloud service that supports a critical or important function. This guide turns that duty into dependency maps, measured data exports, staged tests and register entries that agree.
Recover a deleted file with S3 Versioning
Recover an S3 object by inspecting retained versions, downloading a known copy, or removing the right delete marker without deleting the recovery data.
Choose an RDS recovery window you can actually restore
Choose RDS backup retention, inspect the real restorable interval, validate an isolated database restore, and record cleanup and recovery limits.
Recover deleted Google Cloud Storage objects with soft delete
Choose a Cloud Storage soft delete window, restore a specific object generation, validate its contents, and account for retention and cleanup.
Set up Cloud SQL backups and prove you can restore
Configure Cloud SQL PostgreSQL backups, understand retention settings, and rehearse a restore through database validation and application cutover.
Recover a deleted Azure blob with soft delete
Choose the right recovery action for a blob, version or container and verify restored bytes.
Recover a deleted Azure Key Vault secret
Distinguish secret recovery from vault recovery and verify versioned application references.
Make PostgreSQL point in time recovery reproducible
Build a version-aware recovery chain from protected base backups and WAL through timeline selection, isolated replay and application acceptance.
Plan Kubernetes drains around the disruption budget
Review selector scope, current status, unhealthy Pod handling and replacement capacity before treating a blocked drain as a reason to bypass availability controls.
Diagnose NAT gateway port exhaustion before adding capacity
Match allocation errors to destination tuples and gateway mode before changing connection pools, addresses or routes.
Separate stopping a fault experiment from recovering the service
Plan AWS FIS around separate evidence for stopping execution, removing fault effects and accepting the recovered application.
Find the EBS limit behind a slow database
Separate volume operation rate, byte rate, instance bandwidth and snapshot initialization before changing storage for a slow database.
Find the shared dependencies behind a cloud outage
Use the June 2025 Google Cloud and Cloudflare reports to review shared runtime, control, identity and recovery dependencies without turning one outage into a provider ranking.
Questions answered
What does Cloud Security Desk cover under Resilience?
Design and testing guidance for containment, restoration, and control-plane recovery under pressure.
Supporting context
Recovery starts with an independent control path.
Why does the resilience topic matter to cloud security?
Recovery starts with an independent control path. This topic applies that principle to practical control evidence and review decisions.
Which control questions belong to Resilience?
Research belongs here when its central evidence, failure mode, or operational decision falls within the resilience boundary described on this page.
How many resilience publications are available?
This page currently lists 38 publications assigned to Resilience.
How should readers use the Resilience research?
Start with the publication closest to the control, platform, or evidence gap under review, then follow its findings, limitations, numbered sources, related work, and downloadable material.
Can resilience overlap other research topics?
Yes. A publication can appear under several topics when one evidence path crosses multiple control boundaries; each publication page identifies its complete scope.
Supporting context