Skip to content
Cloud Security DeskSearch
Menu

Research topic

Resilience

Recovery starts with an independent control path.

38 publications

Design and testing guidance for containment, restoration, and control-plane recovery under pressure.

View every topic

From the desk

38 publications
Technical guide · August 28, 2026 · Source-based analysis

Recovery objectives that match the cloud service

Define the business function, outage clock, recoverable data and dependency assumptions before choosing a cloud disaster-recovery architecture.

Technical guide · August 28, 2026 · Source-based analysis

A controlled return from the SQS dead letter queue

Repair the failure, check consumer compatibility and return failed work with a bounded rate, observable stop conditions and business reconciliation.

Technical guide · August 28, 2026 · Source-based analysis

Error budgets for controlled service degradation

Protect essential work under load while counting rejected and degraded requests against the service promise that users were actually given.

Technical guide · August 28, 2026 · Source-based analysis

Certificate renewal under shorter validity limits

Use the public TLS issuance schedule to review authorization, renewal, deployment and independent verification of the certificate an endpoint actually serves.

Technical guide · August 28, 2026 · Source-based analysis

The bottlenecks that shape a cloud DDoS response

Distinguish bandwidth, packet processing, connection state and application work before choosing a DDoS response or assuming the whole service path is protected.

Technical guide · August 28, 2026 · Source-based analysis

Where DNS failover loses control of the clock

Separate authoritative routing, resolver caches, stale answers, runtime caching and existing connections when describing what DNS failover can achieve.

Technical guide · Published August 28, 2026 · Source-based analysisSeries August 26, 2026

Keep database changes compatible with application rollback

Preserve an explicit relationship between old code and migrated state through additive changes, safe backfills, and a defined rollback window.

Research note · Published August 28, 2026 · Source-based analysisSeries July 17, 2026

Stop retries from amplifying an outage

Count attempts across the complete request path, give retries a finite owner and budget, and define how repeated intent avoids duplicate side effects.

Technical guide · Published August 28, 2026 · Source-based analysisSeries June 7, 2026

Keep encryption keys recoverable with the data they protect

Trace each encrypted recovery point to its required key, usable lifecycle state, and restore permissions before retiring cryptographic dependencies.

Technical guide · Published August 28, 2026 · Source-based analysisSeries April 28, 2026

Make regional failover work without new infrastructure

Prepare capacity, dependencies, and the routing control path before an incident, then measure when clients reach an accepted recovery service.

Technical guide · Published August 28, 2026 · Source-based analysisSeries March 19, 2026

Measure recovery by the service you can restore

Define application acceptance, recoverable data, and a complete timeline before treating a completed restore job as proof of recovery.

Technical guide · Published August 28, 2026 · Source-based analysisSeries February 7, 2026

Protect backup copies from the account that runs production

Map deletion authority, retention protection, keys, and recovery identities so a surviving backup has a usable path back to service.

Research report · August 26, 2026 · Desk publication

Qwen3.8-Flash-Next and GLM-5.3-Flash share a 3:1 long-context pattern

Both models replace most conventional attention layers with recurrent state and reserve sparse attention for periodic retrieval. Their differences lie in where they place capacity, how much neural computation they activate, and what their serving stacks must keep trustworthy.

Technical guide · July 3, 2026 · Illustrative analysis

Recover the control plane before you need it

A recovery plan that depends on the compromised identity system is an aspiration. Build and test an independent administrative path.